Hi, On Sat, Oct 26, 2013 at 05:37:33AM +0600, Denis Fateyev wrote: > On Sat, Oct 26, 2013 at 5:21 AM, Sébastien Luttringer > <[email protected]>wrote: > > So why not keep sysconfdir and set a default value to /etc/smtpd > > (default pool is /var/spool/smtpd) instead of using a non standard > > new value? > > The default value should be then `/etc/opensmtpd` [...] > > Hardcoded `%{sysconfdir}/opensmtpd` for config path is better than the > current situation. I think it should be ok.
That would be fine by me. Looking at the GNU Coding Standards[0],
`sysconfdir' is described as:
The directory for installing read-only data files that pertain to a
single machine–that is to say, files for configuring a host. Mailer
and network configuration files, /etc/passwd, and so forth belong
here.
Thus, to my understanding, sysconfdir would correspond to /etc (at least
for Debian, potentially /usr/local/etc for other systems). Setting
sysconfdir to /etc/opensmtpd doesn't make sense to me, since nobody
would put their passwd file under /etc/opensmtpd. I would assume that
software projects are expected to place their configuration files either
directly under "%(sysconfdir)" (e.g., /etc/frobnicator.conf), or in a
specific subdirectory of "%(sysconfdir)" (e.g.,
/etc/frob/frobnicator.conf), and this at their own discretion.
Presumably projects with only one config file would opt for the first
alternative, those with multiple config files would hopefully opt for
the second alternative.
On Sat, Oct 26, 2013 at 07:20:09AM +0600, Denis Fateyev wrote:
> You can name it `package configuration directory` or `global system
> one`, because now they are the same in the package configure logic.
> They should be divided in some way, that's my point.
I can think of two solutions to the above request.
1) Only have sysconfdir as an option as described in Denis' above email
and then:
a) Install aliases to %(sysconfdir)/aliases
b) Install all other config files to %(sysconfdir)/opensmtpd/*,
hardcoding the "%(sysconfdir)/opensmtpd/" part (this is easily
patchable by package maintainers)
2) Add an additional option specifying the subdirectory under which
opensmtpd-specific config files should go, say "localconfdir", which
defaults to "%(sysconfdir)/opensmtpd/":
a) Install aliases to %(sysconfdir)
b) Install all other config files to %(localconfdir).
On Sat, Oct 26, 2013 at 07:01:01PM +0600, Denis Fateyev wrote:
> On Sat, Oct 26, 2013 at 11:04 AM, Sébastien Luttringer
> <[email protected]>wrote:
> > Nothing wrong with this substitution. opensmtpd alias config file
> > should be inside opensmtpd configuration directory.
>
> It shouldn't. At least, in Debian and Fedora.
I agree with Denis. The Debian package will never place the alias config
file inside an opensmtpd-specific configuration directory (e.g.,
`/etc/opensmtpd/'). In Debian, the location of the aliases file is
stipulated to be `/etc/aliases' by Debian Policy Manual §11.6, "Mail
transport, delivery and user agents"[1]:
/etc/aliases is the source file for the system mail aliases (e.g.,
postmaster, usenet, etc.), it is the one which the sysadmin and
postinst scripts may edit. After /etc/aliases is edited the program
or human editing it must call newaliases. [...]
I believe the rationale for this is that users can then freely switch
between MTAs without having to worry about copying an aliases file
between package-specific directories, and any utility modifying aliases
only needs to be aware of one aliases file location.
> Right now Debian package uses `/etc/smtpd.conf` (
> http://packages.debian.org/en/sid/amd64/opensmtpd/filelist ) They
> don't have the problem we are discussing because they have everything
> in `/etc`. If they decide to change configuration directory, they face
> the same issue.
I don't have any plans to change the config directory in the forseeable
future, unless the upstream default for the portable branch changes. If
upstream plans on moving to /etc/opensmtpd/smtpd.conf or something, then
Debian will naturally follow. My goal is always to minimise the amount
of Debian-specific changes to the opensmtpd package. I don't mind
backporting patches for issues reported by users, or making
Debian-specific patches where required by Debian Policy, but that's the
pretty much the extent of changes I'm currently willing to make.
I hope this helps clarify how the proposed changes would affect Debian.
Best wishes,
Ryan
[0] http://www.gnu.org/prep/standards/html_node/Directory-Variables.html
[1]
http://www.debian.org/doc/debian-policy/ch-customized-programs.html#s-mail-transport-agents
--
|_)|_/ Ryan Kavanagh | Debian Developer
| \| \ http://ryanak.ca/ | GPG Key 4A11C97A
signature.asc
Description: Digital signature
