build against Heimdal Kerberos libraries

[Jeremy Jackson]

Untested but shows no problems when recompiling libneon26 (dpkg-buildpkg) with heimdal-dev instead of MIT on Feisty. Changing dependency on krb5-dev to "krb5-dev | heimdal-dev" in debian/control would be a first step. My ultimate goal is Heimdal's in-memory credentials cache (which is working with the above changes) which could enable a user session Identity Manager.

I would like to see heimdal as the default build but I'm sure there will be more discussion first. At least being able to say it *can* build with heimdal will help when enumerating packages that need to be migrated.

[Michael Bienia (geser)]

The 'main' component must be self-containing: packages from main must only depend (and build-depend) on packages in main.

neon26 and krb5 are both in main, but heimdal is in universe.

To change this you would need to get heimdal included in main to be able to build-depend on it in neon26.

The best place to figure out if such a change is possible would be the ubuntu-devel-discuss mailing list.

[C de-Avillez (hggdh2)]

Closing as duplicate of bug 125807

[C de-Avillez (hggdh2)]

Duh. It would really help if I could at least read what package is involved. This is not a duplicate of the above bug. Setting as incomplete/Wishlist.

[Launchpad Janitor (janitor)]

[Expired for neon26 (Ubuntu) because there has been no activity for 60 days.]

[Colin Watson (cjwatson)]

The first comment in this bug was not accurate. A package in main may list a package in universe as an alternate build-dependency, provided that its build-dependencies are in some way satisfiable in main. From an archive point of view, Jeremy's suggestion is perfectly valid (though I don't know neon well).