Qmail
[Top] [All Lists]

Re: qmail Patch Repository

To: Qmail mailing list <qmail@list.cr.yp.to>
Subject: Re: qmail Patch Repository
From: Charles Cazabon <qmail@discworld.dyndns.org>
Date: Wed, 28 Feb 2007 09:53:40 -0600
Delivered-to: sp-com-lists@consult.net
Delivered-to: gmail-qmail@securepoint.com
Delivered-to: sp.com.list@gmail.com
Delivered-to: mailing list qmail@list.cr.yp.to
In-reply-to: <20070228151607.GB24361@nachos.phaseit.com>
Mail-followup-to: Qmail mailing list <qmail@list.cr.yp.to>
Mailing-list: contact qmail-help@list.cr.yp.to; run by ezmlm
References: <45E59056.50008@cmcflex.com> <20070228151607.GB24361@nachos.phaseit.com>
User-agent: Mutt/1.5.11
Fabio Busatto <fabio.busatto@sikurezza.org> wrote:
> On Wed, Feb 28, 2007 at 07:23:18AM -0700, mlist wrote:
> > Sounds like a great idea to me.  It would help if the patches were 
> > categorized . . . I guess kind of like how squirrelmail has their 
> > plugins section organized? http://www.squirrelmail.org/plugins.php
> 
> Yes, this is reasonable.
> The idea is to create a system like the kernel, using a .config file
> and a pool of #ifdef preprocessor directives.

Note that scattering tons of preprocessor conditionals through djb's code is
going to make it *less* readable and significantly increase the chances of
introducing bugs, possibly including security holes.

Fair warning.

Charles
-- 
--------------------------------------------------------------------------
Charles Cazabon                               <qmail@discworld.dyndns.org>
Read http://pyropus.ca/personal/writings/12-steps-to-qmail-list-bliss.html
My services include qmail consulting.  See http://pyropus.ca/ for details.
--------------------------------------------------------------------------

<Prev in Thread] Current Thread [Next in Thread>