On Wed, Jun 19, 2013 at 01:41:36AM +0600, Denis Fateyev wrote:
> Hello there,
> 
> > [...]
> >
> > Long story short, we install in libexec because this is the proper place
> > when we're on a system with a mailwrapper or mailwrapper-like mechanism.
> > But since the mailwrapper exposes programs in bin and sbin paths, a link
> > is created to cope with that in the portable version.
> >
> > This needs to be fixed, but the solution is not just to remove the links
> > and so we need to have a discussion with Charles first. We'll do that in
> > public when he is back from wherever he is roaming :-)
> 
> [...]
>
> The best approach is to install 'real' binaries (smtpd, smtpscript,
> mail.local, smtpctl, makemap) during "make install" phase directly to
> 'bindir' and 'sbindir', without any of links and whatever, and let
> packagers decide about needed links, places and filenames according
> requirements of the 'alternatives' system they're using (if any).
>

I don't know if it's the best approach.
I would tend to prefer an approach where a configure option can be given
to have the libexec stuff installed there:

   ./configure --prefix=/usr/local
   installs in /usr/local/{bin,sbin}

   ./configure --prefix=/usr/local --use-libexec
   installs in /usr/local/{bin,sbin} + /usr/local/libexec

That's just a *quick idea* to illustrate that the solution could be
between keeping libexec like today and getting completely rid of it
like you suggest.

Whatever we decide, it will be when Charles is back from vacation
anyways, I don't want him to come back and be surprised with that
change without him even being involved in the discussion ;-)


> In short, the existing mailwrapper-tolerant mechanism doesn't solve
> anything on Linux out-of-box. Having this, we need to rename and/or reorder
> things anyway, changing them from mailwrapper-like to
> our-alternatives-like. So, it would better to become initial set of
> binaries as much as simpler, without mailwrapper inheritance.
> 

You should keep "Linux" out of the equation, we want to find solutions
that accomodate all systems we run on (FreeBSD, NetBSD, Dragonfly, OSX
and Linux) and we don't want to accomodate just the most popular :-)

A generic solution like the "--with-libexec" would for example make the
situation better for your system and others without mailwrappers, while
still providing the libexec/ indirection for systems that use them.


-- 
Gilles Chehade

https://www.poolp.org                                          @poolpOrg

-- 
You received this email because you are subscribed to mailing list: 
[email protected]
To unsubscribe, send mail with subject:
        [[email protected]] unregister

Reply via email to