Major changes to Heimdal in Heimdal 0.3e-5

[Brian May <bam@debian.org>]

Hello,

My next upload of Heimdal will have the following major changes:

- will use krb5-config package as being developed by Sam.

- uses libtool 1.4, so library interdependency problems are solved.

- splits heimdal-lib up into multiple libraries:

 libasn1-2-heimdal - Libraries for Heimdal Kerberos
 libcomerr1-heimdal - Libraries for Heimdal Kerberos
 libgssapi1-heimdal - Libraries for Heimdal Kerberos
 libhdb7-heimdal - Libraries for Heimdal Kerberos
 libkadm5clnt4-heimdal - Libraries for Heimdal Kerberos
 libkadm5srv7-heimdal - Libraries for Heimdal Kerberos
 libkrb5-15-heimdal - Libraries for Heimdal Kerberos
 libotp0-heimdal - Libraries for Heimdal Kerberos
 libroken9-heimdal - Libraries for Heimdal Kerberos
 libsl0-heimdal - Libraries for Heimdal Kerberos
 libss0-heimdal - Libraries for Heimdal Kerberos

this ensures backward compatibility can be achieved.

the -heimdal postfix is to ensure no conflicts in package names will
occur.

Yes, the package descriptions probably should be improved ;-), but
this is currently not a high priority[2].

- will maintain a dummy heimdal-lib package, as the existing one will
remove /etc/krb5.conf on purge.

NOTE TO ALL PACKAGES THAT COMPILE USING HEIMDAL:

You should no longer link[1] against the assorted array of libraries.
Instead, you should only link against -lgssapi or -lkrb5. The other
libraries required will be pulled in automatically.

Or, better still, use the krb5-config script which will always return
the correct libraries, even if using Heimdal from upstream (which have
not changed to use libtool 1.4 yet).

WHEN THIS WILL OCCUR:

I have several minor jobs to do: create dummy heimdal-lib package,
update changelog entry, etc. I am currently recompiling a new package
with these changes.


Then I will upload it as soon as Sam's krb5-config package is
uploaded.

LIMITATIONS:

upstream haven't started using libtool 1.4 yet, but I have submitted a
patch which gets the library dependencies correct.

NOTE:

[1] Of course, this does not apply if the code really does use
features from other libraries.  These libraries still need to be
specified (don't rely on them being pulled in automatically).

[2] currently I have hacked a method of automatically inserting the
major library version numbers into the library names in
debian/control, so this task doesn't have to be done
manually. However, it makes editing the descriptions harder.  Yuck. I
will have to see if I can simplify this at all. Any ideas how it
should be done properly? I tried using output substitution variables,
but that doesn't work for package names.
-- 
Brian May <bam@debian.org>