From: Till Kamppeter <till.kamppeter@gmail.com>
To: "Wichmann, Mats D" <mats.d.wichmann@intel.com>
Cc: wendyp@jurassic.eng.sun.com, rusty@samba.org,
printing-architecture <printing-architecture@freestandards.org>,
"McDonald, Ira" <imcdonald@sharplabs.com>,
Wendy Phillips <wendy.phillips@sun.com>
Subject: Re: [Printing-architecture] Proposed filesystem layout for print ppd and driver files
Date: Wed, 02 Aug 2006 18:41:09 +0200 [thread overview]
Message-ID: <44D0D5A5.7070900@gmail.com> (raw)
In-Reply-To: <3F62CBEE02D6404E98C65934617EB58254DED6@fmsmsx414.amr.corp.intel.com>
Wichmann, Mats D wrote:
>>>Except that I do NOT agree that the symlinks should be
>>>mandatory - if a print software vendor wants to store
>>>directly and ONLY in '/opt/share/ppd/<supplier>/<mfg>',
>>>that is sufficient and _preferable_ to the creation of
>>>more '/opt/<supplier>' directories for a useless level
>>>of indirection.
>>
>>Does the FHS allow files other than symlinks in subdirectories of
>>/opt/share/ and /opt/lib?
>
>
> Yes, but it does not allow a software packager to
> put them there.
>
> "The directories /opt/bin, /opt/doc, /opt/include, /opt/info, /opt/lib,
> and /opt/man are reserved for local system administrator use. Packages
> may provide "front-end" files intended to be placed in (by linking or
> copying) these reserved directories by the local system administrator,
> but must function normally in the absence of these reserved
> directories."
>
> (so it doesn't mention /opt/share explicitly but it seems
> like the intent is clear)
>
Does this mean that for third-party vendors only
/opt/<supplier>/
is allowed and nothing outside of this?
Then I see the only solution in
/opt/<supplier>/ppd/<file>.ppd
for the PPD files of this supplier and requiring absolute paths in the
PPD to the driver, which can be at an arbitrary place in /opt/<supplier>/.
WDYT?
Till
next parent reply other threads:[~2006-08-02 16:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3F62CBEE02D6404E98C65934617EB58254DED6@fmsmsx414.amr.corp.intel.com>
2006-08-02 16:41 ` Till Kamppeter [this message]
2006-08-03 1:28 ` [Printing-architecture] Proposed filesystem layout for print ppd and driver files Christopher Yeoh
2006-08-03 13:52 ` Till Kamppeter
[not found] <3F62CBEE02D6404E98C65934617EB582586CB7@fmsmsx414.amr.corp.intel.com>
2006-08-03 14:39 ` Till Kamppeter
2006-08-02 16:18 McDonald, Ira
2006-08-02 16:25 ` Till Kamppeter
-- strict thread matches above, loose matches on Subject: below --
2006-07-27 0:43 Wendy Phillips
2006-07-27 4:29 ` Christopher Yeoh
2006-08-02 16:05 ` 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=44D0D5A5.7070900@gmail.com \
--to=till.kamppeter@gmail.com \
--cc=imcdonald@sharplabs.com \
--cc=mats.d.wichmann@intel.com \
--cc=printing-architecture@freestandards.org \
--cc=rusty@samba.org \
--cc=wendy.phillips@sun.com \
--cc=wendyp@jurassic.eng.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.