Fabio Busatto wrote:
On Wed, Feb 28, 2007 at 10:14:24AM -0500, Amitai Schlair wrote:
Looks interesting. The pkgsrc package of qmail does something
somewhat similar, though it's specifically non-interactive (pkgsrc
wants to build without bothering anyone). I declare
PKG_OPTIONS.qmail= qmail-netqmail qmail-bigdns qmail-realrcptto qmail-
viruscan syncdir
in /etc/mk.conf and all the right stuff happens at build time. :-)
Sounds good, but in my opinion one of the principles of this project
should be the independence from specific distributions, architectures,
operative systems and so on.
Our motto can be: if you can run qmail, you can run iloveqmail(?) too.
Personally, I would prefer something like an 'conf-iloveqmail' with an
easy to read
text file, well commented, that allows you to select patches or
combinations of patches
and makes note of any dependencies/conflicts in each line.
This isn't how a linux kernel (bloat :P) is built, but it is how
something like a FreeBSD
(very free) is built. Then I wouldn't mind an option to save that to a
different filename
so that from one source tree, I could do something on the order of:
# make build iloveqmail QMAILCONF=STANDALONE
...
# make install iloveqmail QMAILCONF=STANDALONE
or
# make build iloveqmail QMAILCONF=CLUSTER1
This way, I could run it under *BSD or *nix at my choosing, and
have the same patchset.
Peter
--
Peter Serwe <peter at infostreet dot com>
http://www.infostreet.com
"The only true sports are bullfighting, mountain climbing and auto racing."
-Earnest Hemingway
"Because everything else requires only one ball." -Unknown
"Do you wanna go fast or suck?" -Mike Kojima
"There are two things no man will admit he cannot do well: drive and make
love." -Sir Stirling Moss
|