Re: limitation in build-depends
>>>>> " " == Brian May <firstname.lastname@example.org> writes:
>>>>> "Julian" == Julian Gilbey <J.D.Gilbey@qmw.ac.uk> writes:
>>> ./configure --with-kb5
>>> And if kb5 is not installed, it just fails instead of
>>> switching to the other.
>>> I don't see a problem there.
Julian> In other words, he has already done this, right? Which is
Julian> what I said right at the start ;-)
> 1. libpam-heimdal does not use autoconfigure. So, no, I do not
> do that ;-).
> 2. autoconfigure scripts sometimes just produce a warning, or
> even worse, totally disregard your specified parameters, if the
> library in question cannot be found (this could be considered a
I would report a bug against such a package.
> Although the worst case situation, if the user does compile
> libpam-heimdal with MIT libraries installed, you would either
> 1. error messages during compilation, as MIT and Heimdal do not
> appear to be source code compatible yet, and libpam-heimdal is
> hard-coded to use comp_heimdal.c, not comp_mit.c
> 2. a libpam-heimdal package that only installs if you have the
> MIT version of Kerberos installed. Which in my opinion isn't
> such a bad thing, just as long as it isn't upload to Debian...
The produced package would depend on the library used, so upon install
apt-get/dselect would want to remove Heimdal and install Mit or vice
versa. The maintainer or administrator should know that something is