rra at debian.org
Fri Nov 20 01:21:14 UTC 2009
Fabian Fagerholm <fabbe at paniq.net> writes:
> Should've sent this email some time ago already, but I totally forgot to
> do it. I currently have very little time to spare for Debian, and I fear
> this is starting to show in the quality of the cyrus-sasl2 package.
> We're accumulating bugs fast. Also, we have one nuisance with the
> package that is hard to spot and has already caused some confusion for
> at least one NMUer: our requirement to (nearly) always release the
> -heimdal package with every version bump.
> What could we do? Is there some way we could automate the -heimdal
> package release?
The best way to fix this problem would be for Sam to have time to finish
the work he was going to do to allow the Heimdal and MIT Kerberos
development packages to be co-installed, or to have someone else with more
time take over that work from him.
The basic idea is reasonably straightforward: install the conflicting
files (include files and *.so links) into per-implementation
subdirectories (/usr/lib/heimdal, /usr/lib/krb5, something like that) in
new packages, and then have the existing libkrb5-dev and corresponding
Heimdal packages depend on those new packages and install symlinks in
/usr/include and /usr/lib. This means no change of behavior for the
people using the current development packages, but Cyrus SASL and others
could install only the new packages, pass the appropriate CPPFLAGS and
LDFLAGS arguments to configure, and do both builds at the same time.
Russ Allbery (rra at debian.org) <http://www.eyrie.org/~eagle/>
More information about the Pkg-cyrus-sasl2-debian-devel