From: Till Kamppeter <till.kamppeter@gmail.com>
To: Christopher Yeoh <cyeoh@samba.org>
Cc: "Printing-Sc (E-mail)" <printing-sc@freestandards.org>,
Michael Sweet <mike@easysw.com>,
printing-architecture <printing-architecture@freestandards.org>,
lsb-discuss <lsb-discuss@freestandards.org>,
freestandards-fhs-discuss@lists.sourceforge.net,
Wendy Phillips <wendy.phillips@sun.com>
Subject: Re: [Printing-architecture] [lsb-discuss] resend notes from lastweek
Date: Tue, 25 Jul 2006 19:50:34 +0200 [thread overview]
Message-ID: <44C659EA.8000602@gmail.com> (raw)
In-Reply-To: <17606.15861.773455.901325@localhost.localdomain>
Christopher Yeoh wrote:
>
> Yea, I agree /opt/vendor appears scattered, but symlinking them in
> through into /opt/lib/ and /opt/share/ should bring them all together
> without the need for adding a special printing directory to /opt. I'd
> like to avoid having a special case here unless it can be shown to be
> really necessary.
>
> We would of course need agreement from all of the major distributions
> before adding this to the FHS.
>
> Note that although 3rd party vendors will only have to install into
> one place, applications that look for them will still need to look in
> /usr/lib and /usr/local/lib in addition to /opt and at a higher level
> someone will need to work out precedence rules (say /usr/local ->
> /opt/ -> /usr in order of decreasing importance)
>
I got the following suggestion from a De Zeurkous <zeurk (at) xs4all.nl>:
------------------------------------------------------------------------
Personally I'd suggest using /usr/opt for this kind of cases, and put all
the relatively generic data in there -- libraries in /usr/opt/lib, manual
pages in /usr/opt/man, perhaps binary symlinks to /usr/opt/bin instead of
in /usr/bin, etc. For the vendor-specific issue, i'd suggest just adding
the supplier tag as a directory and then symlinking back --
/usr/opt/lib/printerdrivers/foo -> /usr/opt/lib/acme/foo and so on.
De Zeurkous
-----------
------------------------------------------------------------------------
I think this is somewhat strange, is this FHS compliant?
Till
next prev parent reply other threads:[~2006-07-25 17:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-25 15:25 [Printing-architecture] [lsb-discuss] resend notes from lastweek Fujinaka, Todd
[not found] ` <17606.15861.773455.901325@localhost.localdomain>
2006-07-25 17:26 ` Till Kamppeter
2006-07-25 17:50 ` Till Kamppeter [this message]
[not found] <3F62CBEE02D6404E98C65934617EB582441EF5@fmsmsx414.amr.corp.intel.com>
2006-07-25 13:06 ` Till Kamppeter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44C659EA.8000602@gmail.com \
--to=till.kamppeter@gmail.com \
--cc=cyeoh@samba.org \
--cc=freestandards-fhs-discuss@lists.sourceforge.net \
--cc=lsb-discuss@freestandards.org \
--cc=mike@easysw.com \
--cc=printing-architecture@freestandards.org \
--cc=printing-sc@freestandards.org \
--cc=wendy.phillips@sun.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.