[lsb-discuss] [Printing-architecture] Agreement on directory structure for printing
Bastian, Waldo
waldo.bastian at intel.com
Tue Aug 8 18:37:06 PDT 2006
The admin paths in section 5 still needs adjustment.
Waldo Bastian
Linux Client Architect - Client Linux Foundation Technology
Channel Platform Solutions Group
Intel Corporation - http://www.intel.com/opensource
OSDL DTL Tech Board Chairman
>-----Original Message-----
>From: Wendy Phillips [mailto:wendy.phillips at sun.com]
>Sent: Tuesday, August 08, 2006 4:58 PM
>To: Till Kamppeter
>Cc: Bastian, Waldo; lsb-discuss; printing-architecture; Printing-Sc (E-
>mail)
>Subject: Re: [Printing-architecture] [lsb-discuss] Agreement on
directory
>structure for printing
>
>Here is a copy of Till's summary with the changes requested by Waldo.
>
>I notice that the links in /opt are not listed as mandatory. This makes
>the task of searching for all PPD files difficult as /opt/<vendor> is
>non-specific.
>
>Is the intent to make the symlinks MUST rather than SHOULD?
>
>-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/<supplier>/<internal structure non specified>
> with symlink(s) to let the PPD files appear in
> /opt/share/ppd/<supplier>/<manufacturer>
>
> b. Installation path for print drivers
> /opt/<supplier>/<internal structure non specified>
> with symlink(s) to let the driver files appear in
> /opt/lib/printdriver/<supplier>/
>
> As the symlink paths are not (yet) registered with LANANA it
> should be taken care of not overwriting anything existing
with
> them. Post-install script should not simply overwrite
> files/directories. In reality a permission of the sys admin
> would be needed, but in practice this is not always possible
as
> post-install scripts called from a package installation need
to
> be non-interactive.
>
>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>
>
>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/<supplier>
> Distro : /usr/share/ppd Lowest
>
> Drivers
> Admin : /usr/local/print/driver Highest
> Third Party Vendor : /opt/<supplier>
> Distro : /usr/lib/printdriver Lowest
>
>
>
>
>
>
>
>
>
>
>Till Kamppeter wrote:
>> 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>
>>> ??
>>
>> _______________________________________________
>> Printing-architecture mailing list
>> Printing-architecture at lists.freestandards.org
>> http://lists.freestandards.org/mailman/listinfo/printing-architecture
More information about the lsb-discuss
mailing list