{snip}
> I'm gonna copy this to the list since you sent it directly to me instead of the
> list :).
There was good reason not to post it to the list.
By the way, I can read to: fields and know how to use reply-to.
(bare some oh-no-seconds).
>
> I don't use LFS I use Gentoo, and sure the emerge product is great, I can do a
> emerge -u world and bang all my packages are up to date. I use it for
> installing the qmail support tools (daemon toos, ucspi-tcp, etc). But I have a
> very good reason to not use the build for qmail, I don't know who set it up and
> they're skill in setting up a qmail installation. Following
> lifewithqmail/lifewithqmailldap is almost as easy as using a package. And I
> know the exact steps that were used to set it up. So if something goes wrong I
> can post a question to either the qmail or qmail-ldap list and say exactly what
> steps were taken. With a package if you have problems I can almost gaurentee
> you that the first thing the experts will say is uninstall whatever package you
> used, then install using lifewithqmail/ldap instructions. If your still having
> problems then ask us again.
Frankly speaking, I don't care too much how you set up your system.
If you need help, and I can help, I probably will.
I have my reasons to look for a way to put qmail-ldap in a .deb
If there is anyone who can help me, fine. If not, fine too.
>
> If you want to make a binary .deb you will not be able to distribute it as
> it is not within the scope of DJB's license for qmail
Hey - great news. I didn't knwo that (not).
> (http://cr.yp.to/qmail/dist.html). I'm not entirely sure but I believe you
> would be able to distribute a source deb that people could build, your best bet
> for that would be to ask on the qmaildist mailing list. Info in above link.
In Debian, qmail is distributed in such a way that the package
downloads first the source, then patches it, then lets you build it
manually with the build-qmail command, then lets you install it with
the dpkg -i command. All the djb things (daemontools, tcpserver,
djbdns) are done this way. Relatively easy. Compliant with the
policies, too.
What I need is a qmail-ldap package that works similar. At the
moment, I patch build-qmail to apply the qmail-ldap patches just
before the actual build. But, as stated before, those patches won't
apply to the sourcetree that the debian packages leaves there. So,
logically, I am looking for a qmail-ldap package, that *does*
install the qmail-ldap patches and then behaves similar to the
existing qmail package. If it's not there, I'll eventually make it.
> Sure if you have 15 or 20 machines in a cluster to install.
I think installing it on more then one machine is enough reason to
make a package. Actually, reinstalling one machine already meets my
criteria for automation.
> building a
> pacakge to do the install would be great. But for me the frequency at which I
> have to install/upgrade my qmail there is no point in taking the time to build
> a package since I build maybe once a year for the server. And that's only if
> Claudio comes up with some amazing bug fix. After all if it ain't broke don't
> fix it right?
Hey - I run a 2 year old patch, and do you hear me complaining ? But
there's a lot of fixes and features, so I am moving ahead.
Maybe this is the wrong list to ask how to integrate qmail-ldap
patch into debian ? Could very well be.
Greetings,
ace
