Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email firstname.lastname@example.org
From: Simon J Mudd (sjmuddpobox.com)
Date: Thu Apr 19 2007 - 16:07:05 CDT
On Thu, Apr 19, 2007 at 03:26:09PM -0400, Victor Duchovni wrote:
> On Thu, Apr 19, 2007 at 08:53:02PM +0200, Simon J Mudd wrote:
> > I'd love to work with others to do something like this but the more
> > generic this becomes the more difficult it is to do well and
> > understandably Wietse only likes "good code" in his tar balls.
> Code quality aside, I really don't think that it is appropriate for
> Postfix to impose its packaging preferences on O/S distributions.
> Packaging *is* the heart of their job, they do it well, Postfix
> makes itself easy to be packaged via the postfix-files interface.
> I think it would be a mistake to bundle code with Postfix that builds
> packages. However if communities of users for a particular platform
> construct re-usable packaging scripts, pointers to these can be provided
> on the add-ons page.
I think the biggest problem is that normally the "distribution/OS" packages
tend not to be very up to date, and perhaps not to upgrade within the same version.
RHEL4 uses postfix-2.1
RHEL5 uses postfix-2.3 (this is only about a month old)
I'm sure other OSes have similar issues.
Unfortunately there are a lot of people who need a more recent version
of Postfix especially because of the spam/virus/... issues and having
a recent version in a packaged format would help a lot.
I "help a bit" with RH Linux, but others do a similar job for OpenPKG,
SuSE, and other OSes. However we all do it differently which means we all
waste time duplicating pretty much the same work. It's just a shame we
can't do it once and let everyone use it. Perhaps I'm just too optimistic
that things like this can be done.
I guess this is drifting a little OT. Sorry.