[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140124113121.GH7283@openwall.com>
Date: Fri, 24 Jan 2014 15:31:21 +0400
From: "(GalaxyMaster)" <galaxy@...nwall.com>
To: owl-dev@...ts.openwall.com
Subject: Re: Postfix 2.11 is ready for commit
Croco,
On Fri, Jan 24, 2014 at 03:16:11PM +0400, croco@...nwall.com wrote:
> I'd say that 'alternatives' is one of these "solutions" that solve some
> imaginary problems while adding new problems, and this time real. Owl is
> not intended for people who can't handle symlinks manually. 'Alternatives'
You clearly are not building enough of packages then :). 'alternatives'
helps a LOT with autotools when one package wants autoconf 2.13, another
autoconf 2.63, etc. Backporting autotools configuration although is
possible, but not feasible -- it's just easier to have the right tool
for the job, IMO.
However, a proper implementation of 'alternatives' is anther matter.
personally, I'm not very happy with most of the existing approaches. In
my mind, such a framework should provide at least two options:
1. to set the system-wide defaults (e.g. when we deploy a hosting
solution for a shared hosting and provide several versions of PHP we
need to specify which one is the default one);
2. a non-privileged user should be able to set their environment
independently (e.g. if I want to use PHP 5.1 and the system-wide default
is 5.5).
Anyway, I kind of deviated from the topic :), sorry.
--
(GM)
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
