Idea for a new appendix

Chris F.A. Johnson chris at home.com
Wed Mar 7 19:42:44 PST 2001


On Wed, 7 Mar 2001, Seth W. Klein wrote:

> Gerard Beekmans wrote:
> >
> > > +1 - so long as there is a note on a package's page informing readers
> > > about the existance of an appendix entry (or a link to it).
> >
> > A link would do. I'm still considering removing the package descriptions from
> > the installation instructions and just keep them in appendix a, with a link
> > on every installation instruction page. Every package could look like the
> > following:
> >
> > Installing Bash
> >
> > Installation of Bash
> >
> > Package description (this will be a link to the proper page in appendix a)
> > Known problems (this will be a link to the proper page in appendix d)
>
> If i see a link that says "Known Problems" i'm going to wonder
> if any of those could bother me and have to check each time. Much
> friendlier would be a link saying "Problems with Redhat 7.x"
> or "Problems with GLIBC 2.0.x" as appropriate.

Or, for brevity's sake, a key: RH7, DEB2.0, etc.

-- 
	Chris F.A. Johnson	    bq933 at torfree.net
	=================================================================
	c.f.a.johnson at home.com	    http://cfaj.freeshell.org
	cfaj at freeshell.org	    http://members.home.net/c.f.a.johnson


-- 
Unsubscribe: send email to lfs-discuss-request at linuxfromscratch.org
and put unsubscribe in the subject header of the message




More information about the lfs-dev mailing list