discuss: Filesystem paths in LDP documentation
Subject:
Re: Filesystem paths in LDP documentation
From:
Mark Komarinski ####@####.####
Date:
13 Apr 2002 23:46:31 -0000
Message-Id: <1018737964.2819.3.camel@jackie>
I think locations like this are specified as part of the Linux Standard
Base (LSB), which Debian follows and RH and others are starting
to follow. My RH7.2 laptop uses /usr/share/doc, for example.
I'd recommend something like this as part of the style guide, but
I can add it to the LAG in the interim.
-Mark
On Sat, 2002-04-13 at 17:40, Charles Curley wrote:
> On Sat, Apr 13, 2002 at 03:41:30PM -0500, David Merrill wrote:
> > On Sat, Apr 13, 2002 at 03:58:45PM +0100, Colin Watson wrote:
> > > Hi,
>
>
> > > The bug opens a wider issue, though. To what extent do readers of this
> > > list think it's reasonable for distributions to patch their LDP packages
> > > to refer to locally-appropriate paths? On the one hand, it may alleviate
> > > confusion when readers find documents referring to paths that aren't on
> > > their systems. On the other hand, the document probably won't be perfect
> > > for each distribution anyway unless the author planned it that way, I
> > > suspect most authors would rather that distributions didn't make local
> > > changes without passing them back, and I doubt I have time to go around
> > > carefully patching the whole LDP all the time.
> >
> > It's always better to get the patch accepted upstream if possible. If
> > you have to patch locally, then so be it. The LDP will work with you
> > to get the fix added by the author, or we'll fix it ourselves if the
> > author does not.
>
> Speaking as an author, I welcome such errata.
>
> Perhaps LDP should also ecourage authors do things like, "This file is
> found in the Blah directory. It is this path on Red Hat X.Y, that path
> on Debian m.n, and may be elsewhere on your system." That will make it
> easy to add new paths as readers or distributors send errata. This may
> be a candidate for the Authors Guide.
>
>
> --
>
> Charles Curley /"\ ASCII Ribbon Campaign
> Looking for fine software \ / Respect for open standards
> and/or writing? X No HTML/RTF in email
> http://w3.trib.com/~ccurley / \ No M$ Word docs in email