All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wendy Phillips <wendy.phillips@sun.com>
To: printing-architecture <printing-architecture@freestandards.org>
Cc: cyeoh@samba.org, mats.d.wichmann@intel.com, wendyp@jurassic.eng.sun.com
Subject: [Printing-architecture] Proposed filesystem layout for print ppd and driver files
Date: Wed, 26 Jul 2006 17:43:05 -0700	[thread overview]
Message-ID: <44C80C19.6040700@sun.com> (raw)

As a result of the past weeks discussion and the fsg architecture 
meeting today, the following proposal is on the table. It defines 
directories for ppd files and print drivers; placement of files is based 
on category of provider: distribution, third party vendor, and system 
administrator.

I have added Chris and Mats as you have been contributing to the 
discussion. If you want to add yourself to the fsg architecture alias, 
it's not high volumne and it would be good to have you.

Regards.

-Wendy


1. Distro supplied files

         The filesystem layout as utilized by the distibutions when the
         ppd files and print drivers are initially installed on the 		 
system. It is presumed that this will also be used for patches 			and 
updates created and delivered by the distro.

         a. Installation path for ppd files
                 /usr/share/ppd/<supplier>/<manufacturer>/

         b. Installation path for print drivers
                 /usr/lib/printdriver/<supplier>

2. Third Party Vendor supplied files

         The filesystem layout to be utilized by third party vendors
         for delivery of ppd files, print drivers and other vendor
         supplied files.

         a. Installation path for PPD files
                 /opt/print/ppd/<supplier>/<manufacturer>

         b. Installation path for print drivers
                 /opt/print/driver/<supplier>

3. Files created, downloaded, or modified by a system administrator.

         a. Installation path for PPD files
                 /usr/local/print/ppd/<supplier>/<manufacturer>

         b. Installation path for print drivers
                 /usr/local/print/driver/<supplier>

4. Common features
         These features apply to each of the three supplier categories,
         distro, third party vendor, and administrator.

         a. PPD file naming convention
                 <MFGString>-<MDLString>-<driver>-<language>.ppd

         b. The contents of the driver directories are entirely
         determined by the supplier.  The path to a driver is found
         by using an absolute path in the ppd file.

         c. Install scripts must be  written in Bourne Shell without
         any extensions.

5. Precedence Rules
         Highest precedence is given to the system administrator which
         allows for system by system modfications as determined by
         support personel.

         PPD files
         Admin :                 /usr/local/print/ppd    Highest
         Third Party Vendor :    /opt/print/ppd
         Distro :                /usr/share/ppd          Lowest

         Drivers
         Admin :                 /usr/local/print/driver Highest
         Third Party Vendor :    /opt/print/driver
         Distro :                /usr/lib/printdriver    Lowest


             reply	other threads:[~2006-07-27  0:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-27  0:43 Wendy Phillips [this message]
2006-07-27  4:29 ` [Printing-architecture] Proposed filesystem layout for print ppd and driver files Christopher Yeoh
2006-08-02 16:05   ` Till Kamppeter
  -- strict thread matches above, loose matches on Subject: below --
2006-08-02 16:18 McDonald, Ira
2006-08-02 16:25 ` Till Kamppeter
     [not found] <3F62CBEE02D6404E98C65934617EB58254DED6@fmsmsx414.amr.corp.intel.com>
2006-08-02 16:41 ` Till Kamppeter
2006-08-03  1:28   ` Christopher Yeoh
2006-08-03 13:52     ` Till Kamppeter
     [not found] <3F62CBEE02D6404E98C65934617EB582586CB7@fmsmsx414.amr.corp.intel.com>
2006-08-03 14:39 ` 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=44C80C19.6040700@sun.com \
    --to=wendy.phillips@sun.com \
    --cc=cyeoh@samba.org \
    --cc=mats.d.wichmann@intel.com \
    --cc=printing-architecture@freestandards.org \
    --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.