On Tue, Apr 09, 2002 at 09:15:26PM +1000, Brian May wrote: > Hello, > > We have the somewhat unusual situation that Heimdal build depends on > kerberoskth and kerberos4kth build depends on Heimdal. > > kerberos4kth depends on heimdal because, this way it can share some low > level libraries which are included in Heimdal. Libraries that don't have > anything to do with Kerberos in fact, such as libroken and libcomerr. > This depends isn't very satisfactory, ideally these libraries need to be > split up into a seperate source stream package, but that isn't going to > happen any time soon. > > heimdal depends on kerberos4kth because it supports kerberos4. > > This worked fine until the move to non-us. > > However, now that the packages have moved into non-us, the builders are > confused because they don't know how to build either package, because it > depends on the other one being built first. > > Mikael's suggestion was that I remove kerberos4 support from Heimdal, > and upload, hence allowing kerberoskth to build. When kerberos4kth is > built, I upload a new version of Heimdal with kerberos4kth re-enabled. > Althought this will break at least on other package while Heimdal > doesn't have kerberos4 support (arla), it shouldn't be for long. > > I was hoping that this could be bypassed though, by telling the > autobuilders to initially resolve the dependancy for heimdal when > building kerberos4tkth from non-us/testing. > > Is this possible? > > Any comments?
A pox on circular build-depends (says one of the new-port builders). The best way to resolve such things, without resorting to trying to trick the autobuilders, is to try to get the porters to rebuild it manually. -- *************************************************************************** Joel Baker System Administrator - lightbearer.com [EMAIL PROTECTED] http://users.lightbearer.com/lucifer/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
