[PATCH] Lynx build docs problem

Dagmar d'Surreal dagmar.wants at nospam.com
Thu Jun 24 20:04:14 PDT 2004

On Thu, 2004-06-24 at 19:08, Randy McMurchy wrote:
> Dagmar d'Surreal wrote:
> > There are a number of issues that should be corrected with the current
> > lynx page...
> > 
> > First off, the latest version is now 2.8.5, not 2.8.4.  Simple enough.
> What book are you looking at? 5.0?
> The latest release is 5.1, and it includes the 2.8.5 version
> of Lynx. CVS, of course, is at the current 2.8.5 release as
> well.
> Though the current instructions don't include the sed "twiddling"
> as the old instruction did, it still passes the docs and help dirs
> to the makes.
> I need to install lynx on a box here. I'll look at your patch.
> Thanks for sending it in. However, in the future, you may want
> to use the current stable version of the book! :-)

Doh!  That was definitely my mistake, and I made another I'll get to in
a moment.  I had a stale link to the book on my toolbar.

Now that I've corrected my bookmark, and re-read over the FHS 2.2 and
2.3 I see that I err'd in the location of the help files.  Especially in
light of --enable-gzip-help to save disk space, the help files are
application-specific, as they are meant to appear as an internal part of
the program, and are definitely not "miscellaneous documentation" (2.2,
2.3) that one reads with less or something.  Since they're
application-specific and architecture independent, they were supposed to
go under /usr/share/lynx_help (clarified in FHS 2.3 by footnote 22).

It also appears that --with-ssl was removed for the newer BLFS, which
astounds me.  Even if OpenSSL is listed as optional, there's a definite
decrease in utility from not linking to it.  Without --with-ssl being
passed to configure, it won't use it at all and SSL transport won't
work, no matter whether OpenSSL or GNUTLS (which people should stay away
from for now IMHO) are installed or not.

(from the other mail)
> I would also argue that the Lynx .html files are not *just* used
> internally by Lynx. You can point any browser to the directory
> and open the lynx_help_main.html file and navigate all Lynx's 
> help from here.

You _can_, but not easily once they're compressed to save space, and
without them being installed, lynx reverts to accessing a copy of them
across the Internet.  Another argument is that no other package's
functionality *breaks* if one should rm -rf /usr/share/doc to save
space.  Should we start moving the yelp/docbook things into
/usr/share/doc now as well?

The patch fixes broken functionality in the shell scripts at build time,
not a run time functionality issue.  I'd argue that blinding someone
with shell variables make less sense for education than simply telling
people that Lynx's build scripts don't follow the FHS at all and put
files in dim-witted places when left to themselves--hence a patch is

New (more correct) version attached.
The email address above is phony because my penis is already large enough, kthx. 
   AIM: evilDagmar  Jabber: evilDagmar at jabber.org (<-not an email address!)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: lynx-2.8.5+fhs.patch
Type: text/x-patch
Size: 3770 bytes
Desc: not available
URL: <http://lists.linuxfromscratch.org/pipermail/blfs-dev/attachments/20040624/fbc902b4/attachment.bin>

More information about the blfs-dev mailing list