Quoting "Ace Suares" <[EMAIL PROTECTED]>:
> Then, it create a directory called qmail-1.03
> Under that dir there is directories:
> build-tree
> debian
> stampdir
> and a lot of .c .h files and some readme's (looks like the source of
> qmail to me).
Right, my fault. The whole point with the patch you got is that it does
_NOT_ come with qmail-original source unpacked. Instead it unpacks the
pristine source, THEN patch it...
Have the ORIGINAL stuff at
ftp://ftp.bayour.com/pub/debian/dists/local/source/Qmail
Then unpack it with
dpkg-source -x qmail_1.03-25.2.dsc
Then go down in the unpacked tree (qmail-1.03/) and execute:
/usr/bin/debuild -rfakeroot -uc -us -B
That will (hopfully) give you three deb's, one of them being
qmail-ldap_1.03-25.2_i386.deb
Take note of what's beeing said in the
debian/changelog
Especially the _THREE_ first entries (version 1.03-25 to 1.03-25.2).
Now, IF all this is ok with you (the change log entries, and the defaults
I have choosen) then you can get the deb (which I'm currently running
live) at
ftp://ftp.bayour.com/pub/debian/dists/local/binary-i386/Qmail/
> That's a pity (for me).
> I'll keep looking around though.
> It's the control-patch that actually bothers me.
> I use domain-based LDAP entries.
> I just want to be able to say:
I'll have a look at this in a couple of weeks. I'm currently about to
move my whole BIND db from bind8 to bind9 and use the LDAP backend.
That will probably need some tuning to QmailLDAP/Controls as well.
IF it does, I'll announce it on the qmail-ldap list as usuall :)
--
747 Albanian genetic bomb quiche Noriega CIA colonel attack North
Korea nuclear Legion of Doom Delta Force Ft. Bragg pits
[See http://www.aclu.org/echelonwatch/index.html for more about this]
