Bernd Wurst wrote:
> I started looking at the courier ebuilds for Gentoo Linux. As I am not a
> developer and my build-process-knowledge is rather limited, I will have to
> ask stupid questions. Please be kind. ;-)
>
If your experience building software is limited, is it wise to use a
platform that depends heavily on building software?
> Gentoo uses some patches to get courier-authlib to compile nowadays. One is
> to
> remove the (seemingly) very outdated and unsupported AC_PROG_SYSCONFTOOL
> Macro from configure.in. When googling for this macro, I only find people
> complaining about broken courier compiles, so this should be removed, IMHO.
>
I also see that in Google, but it seems to be limited to Gentoo users
and people trying to build from CVS without following the instructions.
sysconftool is a part of Courier, and isn't likely to be removed unless
the configuration system changes significantly. By removing sysconftool
from the Gentoo build, the maintainer has made it more difficult to
upgrade Courier on Gentoo systems. Without sysconftool, an update will
overwrite local configuration changes, and reset them to their defaults.
> The gentoo ebuild also alters authmigrate.in with the following sed calls:
> sed -i -e "s|^chk_file .* |&\${DESTDIR}|g" authmigrate.in
>
That doesn't make much sense anywhere but Gentoo. It looks like it'll
check for pre-authlib versions of those files, and package them if it's
executed at package build time. That's not the intended use of the
script, and isn't useful unless your build system and your production
system are the same host (which is an awful idea).
> sed -i -e'/for dir in/a@@INDENT@@/etc/courier-imap \\' authmigrate.in
> sed -i -e'/for dir in/a@@INDENT@@/etc/courier/authlib \\' authmigrate.in
> sed -i -e"s|@@INDENT@@| |g" authmigrate.in
>
Also probably only useful in Gentoo, since that's the only system that
uses those installation prefixes.
> sed -i -e"s|\$sbindir/makeuserdb||g" authmigrate.in
>
This is also only needed if you run authmigrate at build time rather
than after installing the package. It's Gentoo-specific, and would
break everyone else's use.
> At last, when only trying to configure courier-authlib, I get this:
>
> | checking for correct ltmain.sh version... no
> | configure: error:
> |
> | *** [Gentoo] sanity check failed! ***
> | *** libtool.m4 and ltmain.sh have a version mismatch! ***
> | *** (libtool.m4 = 1.5.26, ltmain.sh = 1.5.22) ***
>
That doesn't seem to be a problem anywhere else, and there's no way to
fix it globally. The courier tarball will always have a different
version of ltmain.sh than *some* platform.
I wonder why Gentoo demands exact matches when no one else does.
> the gentoo-solution is to completely re-run all these voodoo-tools (autoconf,
> automake, libtool) that consume more time than the compile itself.
>
configure takes a long time to run because courier is a very modular
project. Many components are reusable, and has its own configure script.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
courier-users mailing list
[email protected]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
