From: Till Kamppeter <till.kamppeter@gmail.com>
To: "Bastian, Waldo" <waldo.bastian@intel.com>
Cc: lsb-discuss <lsb-discuss@freestandards.org>,
printing-architecture <printing-architecture@freestandards.org>,
"Printing-Sc (E-mail)" <printing-sc@freestandards.org>
Subject: Re: [Printing-architecture] [lsb-discuss] Agreement on directory structure for printing
Date: Mon, 07 Aug 2006 17:52:45 +0200 [thread overview]
Message-ID: <44D761CD.9000806@gmail.com> (raw)
In-Reply-To: <1B47D24854C7BC4FA8DA28BEBB59B0BA4176AE@orsmsx419.amr.corp.intel.com>
Thank you for this, i have not seen that Wendy suggested something
completely different for /usr/local/. What I mean is this:
---------------------------------------------------------------------
3. Files created, downloaded, or modified by a system administrator.
a. Installation path for PPD files
/usr/local/share/ppd/<supplier>/<manufacturer>
b. Installation path for print drivers
/usr/local/lib/printdriver/<supplier>
---------------------------------------------------------------------
This way it is the very same structure as in /usr/ and/opt/.
Till
Bastian, Waldo wrote:
> Given these directories:
> /usr/share/ppd/<supplier>/<manufacturer>/
> /usr/lib/printdriver/<supplier>
> Is there any particular reason for using
> /usr/local/print/ppd/<supplier>/<manufacturer>
> /usr/local/print/driver/<supplier>
> Instead of
> /usr/local/share/ppd/<supplier>/<manufacturer>
> /usr/local/lib/printdriver/<supplier>
> ??
next parent reply other threads:[~2006-08-07 15:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1B47D24854C7BC4FA8DA28BEBB59B0BA4176AE@orsmsx419.amr.corp.intel.com>
2006-08-07 15:52 ` Till Kamppeter [this message]
2006-08-08 23:58 ` [Printing-architecture] [lsb-discuss] Agreement on directory structure for printing Wendy Phillips
[not found] <1B47D24854C7BC4FA8DA28BEBB59B0BA463262@orsmsx419.amr.corp.intel.com>
2006-08-09 16:52 ` Till Kamppeter
[not found] ` <m3fyg4pmm8.fsf@gromit.moeb>
2006-08-11 1:30 ` Christopher Yeoh
2006-08-11 2:06 ` Michael Sweet
2006-08-14 17:10 ` Till Kamppeter
2006-08-17 15:56 ` Till Kamppeter
[not found] <3F62CBEE02D6404E98C65934617EB58268B93F@fmsmsx414.amr.corp.intel.com>
2006-08-14 17:30 ` Till Kamppeter
2006-08-17 17:45 McDonald, Ira
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=44D761CD.9000806@gmail.com \
--to=till.kamppeter@gmail.com \
--cc=lsb-discuss@freestandards.org \
--cc=printing-architecture@freestandards.org \
--cc=printing-sc@freestandards.org \
--cc=waldo.bastian@intel.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.