All of lore.kernel.org
 help / color / mirror / Atom feed
From: Till Kamppeter <till.kamppeter@gmail.com>
To: "McDonald, Ira" <imcdonald@sharplabs.com>
Cc: mats.d.wichmann@intel.com, wendyp@jurassic.eng.sun.com,
	rusty@samba.org,
	printing-architecture <printing-architecture@freestandards.org>,
	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:25:32 +0200	[thread overview]
Message-ID: <44D0D1FC.5050604@gmail.com> (raw)
In-Reply-To: <789E617C880666438EDEE30C2A3E8D10EEA3@mailsrvnt05.enet.sharplabs.com>

McDonald, Ira wrote:
> Hi Till,
> 
> I mostly agree with this set of directory paths - thanks for
> writing up the summary.
> 
> I think that full FHS compliance is important - partly because
> it's a requirement for inclusion in LSB - and partly because
> I dislike "reinventing the wheel".
> 
> 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?

   Till


  reply	other threads:[~2006-08-02 16:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-02 16:18 [Printing-architecture] Proposed filesystem layout for print ppd and driver files McDonald, Ira
2006-08-02 16:25 ` Till Kamppeter [this message]
     [not found] <3F62CBEE02D6404E98C65934617EB582586CB7@fmsmsx414.amr.corp.intel.com>
2006-08-03 14:39 ` 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
  -- 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=44D0D1FC.5050604@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.