All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guillaume Rousse <Guillaume.Rousse@inria.fr>
To: Jeff Moyer <jmoyer@redhat.com>
Cc: autofs@linux.kernel.org
Subject: Re: [ANNOUNCE] autofs 5.0.1 rc3 release candidate
Date: Wed, 17 Jan 2007 15:00:18 +0100	[thread overview]
Message-ID: <45AE2BF2.5020907@inria.fr> (raw)
In-Reply-To: <x49k5zl7ort.fsf@segfault.boston.devel.redhat.com>

Also sprach Jeff Moyer:
> ==> On Wed, 17 Jan 2007 11:59:49 +0100, Guillaume Rousse <Guillaume.Rousse@inria.fr> said:
> 
> Guillaume> - autofs-5.0.1-rc3-separate-config-files.patch split configuration in
> Guillaume> two parts, one for the automount daemon, one for the automount init script
> 
> What is the purpose of this?
Well, to mimic standard setup for all other services.

I also think separating vendor-specific parts, such as init scripts,
from upstream parts, such as main daemon configuration, make life easier
for both parts.

It's easier for packagers to provide vendor-specific customisation
without side effects (I'd prefer avoiding to add a
USE_MDV_SPECIFIC_FEATURE_X in autofs configuration). And it avoid
upstream maintainer to provide vendor-targeted switches, such as
--where-do-you-want-the-automount-configuration-to-be-installed, as this
 standard (%sysconfdir).

  reply	other threads:[~2007-01-17 14:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-04 13:09 [ANNOUNCE] autofs 5.0.1 rc3 release candidate Ian Kent
2007-01-17 10:59 ` Guillaume Rousse
2007-01-17 13:36   ` Ian Kent
2007-01-17 13:42   ` Jeff Moyer
2007-01-17 14:00     ` Guillaume Rousse [this message]
2007-01-17 14:08       ` Jeff Moyer
2007-01-17 14:50         ` Ian Kent

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=45AE2BF2.5020907@inria.fr \
    --to=guillaume.rousse@inria.fr \
    --cc=autofs@linux.kernel.org \
    --cc=jmoyer@redhat.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.