Re: maildrop build fails: debian/rules build exit status 2, Questions about building debs
Sam Varshavchik <[email protected]> Sat, 13 Jul 2024 07:36:15 -0400
| Newsgroups | gmane.mail.imap.courier.general |
|---|---|
| Message-ID | <[email protected]> |
datenritter writes: > Hi there, > > long time courier user here, also slightly fed up with the Debian situation. > We need to fix this. Anyway... > > I could use a little help with the build process. As I don't want to compile > on the production machine, I tried to create debs with the tarball-method: > > > 1. Can I somehow pass options to 'configure' when running the 'courier- > debuild' script so I could customize my build? > (Should I anyway? Or could I mess up the creation of debs if I did?) Debian packaging is oriented to using a fixed set of configure options. It might be possible to edit packaging/debian/rules and stick your configure options in there before running courier-debuild. Not sure if it'll work. > 2. I have already created (and installed) debs for courier-unicode, courier- > authlib and courier-imap with courier-debuild -us -uc. > > The maildrop build runs into an error with some testsuite: This should already be fixed in the build from the download page dated 20231229. I've been tardy in making a new release of maildrop, I'll get to it soon but for now you can grab that build. > 3. Is there a way to do this from the source you just pull from github? The > tarball-method looks a bit quirky to me. Maybe there's a build-deb target...? No there isn't. The git repository does not include autotools-generated scripting. It might be possible to put together an automated system that assembles the source tree from BOTH courier and courier-libs repositories, runs autobloat, runs configure with default options, then make, then make dist, which produces the packaged tarball, and then use the existing process starting with that tarball. _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
signature.asc
(application/pgp-signature, 228 B)
-----BEGIN PGP SIGNATURE----- iHUEABYKAB0WIQRupkKLJP96aW75pIOKYPgoojZS4gUCZpJmrwAKCRCKYPgoojZS 4irrAQCb+HMTYzQ/kY/ILLewvtffywZOjpLh6gON0mZp3e+Q0wEA40JgELSW0Jpz 4Zj+AAu8how5zPT409XYN/38FLoqDQE= =X1Md -----END PGP SIGNATURE-----