[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Idea : common dir and tree (Rep:Re: Why not create packages?)
Guylhem Aznar wrote:
> I still use /usr/dangerous :-) where I install the software I compile,
> while I prefer /opt/ for precompiled or huge compiled packages
> (inn+articles)
My reading of the FHS is that /usr/local is for packages compiled
and installed locally whereas /opt is for major packages that have
been packaged by the manufacturer. Thus if we use /opt/LDP we are
also expected to actually makes the package that populates a tree
structure of directories below the /opt/LDP root.
> But your comment is very adequate, I suggest we use :
> /usr/share/doc/ldp
> /usr/share/doc/ldp/HOWTO
> /usr/share/doc/ldp/HOWTO/pdf
> (...)
Many would expect to find a /usr/share/doc/HOWTO from the old
days so we might make a link.
Then again the /usr/share/HOWTO might contain non-LDP HOWTOs
such as those from OSWG in which case we shouldn't make links
that gives the impression LDP HOWTOs are the only ones.
> for the packaged documentation, while :
> /opt/ldp
> /opt/ldp/HOWTO
> /opt/ldp/HOWTO/pdf
> (...)
>
> would be used for the HOWTO packages (deb, rpm...) soon available from
> linuxdoc.org
That would be in line with the FHS.
> DocBrowser could easilly parse both directories, the later superceding
> the former, to present the users a good interface to documentation.
It might be an idea to make allowances for /opt/OSWG appearing.
> man page, info files and "foreign" doc in /usr/doc could be handled
> either by symlinks or by coding a search routine in the standard paths.
The FHS specifies the man page paths already.
Regards,
Stein Gjoen
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]