Based on our discussion with 'seemant' the requirement for FHS locations result
in different packages overlapping in a single location. 'seemant' promised to
offer a solution for concurrent installation of kth-krb4 and heimdal. So? ;)
Second, I've found even other packages causing overlaps, just by luck I hit
klist from java. :((
... what else do we have it? ... in mit-krb, yes too
Similarly, kpasswd is in multiple packages (one of them is openafs).
Martin (or shall I call you 'martin'?),
Thanks for filing the bug about kth-krb + heimdal -- I'll investigate shortly.
As for klist and kpasswd -- whether they are in FHS locations (prefixed with
package name, if they do indeed serve different purposes) or in /usr/athena and
/usr/heimdal and /opt/blackdown-jdk-some-really-long-string-of-numbers/bin/
there will still be a pecking order in the PATH, so you have the negatives of
the same package name there as well (even if the "namespace" -- herein referring
to the parent path -- is different). There is ambiguity regardless. Yes, so we
don't overwrite them -- but the problem isn't _solved_ with non-fhs locations,
it is simply masked.
Sorry that I call you 'seemant', I just remember only the login name, and even
when I see "Seemant Kulleen" I don't know which name is teh first. :(
Was not meant offensive in any way.
I think people used to use kerberos packages are often aware of that and
although this is not a justification for me, I don't think software packagers
should rename programs. I think this is the task for upstream maintaners.
I brought this up as you asked for it and second, I thought this bug report
might serve as a list of other filename clashes. It seems 'stefaan' might get
openafs running and detected by other packages. I filed in the meantime couple
other upstream bugreports so things might change and I might even vote for FHS.
;) If you provide the support, why not. I'm certainly willing to help as you
know, although am convinced that people who *already do run afs* on their
machines have it in transarc paths and do not have a reason to shuffle around
configs and wait for etc-update to suddenly overwrite their config files after
hitting "-5". ;)
Back to heimdal ... I think you should not rename klist, kpasswd etc. but rather
educate users and possibly, maybe one could figure out the ordering within PATH
based on the combination of USE flags. Actually, in one of the already closed
bugreports I've proposed USE flags like heimdal-krb4, krb4-heimdal and possibly
even triplets could be introduced. I remember now, I proposed them because there
was unresolved problem that configure of program X had to take precedence of
heimdal over kth-krb4 in one case, in other case make fallback support from
heimdal to kth-krb4 as well. That was I think the reason in that particular
case. I'm sure you will find a way how to construct the ordering with PATH
variable and how to instruct configures.
app-crypt/kth-krb has been removed 8+ months ago for bug #173354; closing.
Still, how about heimdal vs. java and mit-krb clashes?
This bug is pending and dead. If you need heimdal I'd like to ask you to use our overlay at git://git.overlays.gentoo.org/proj/kerberos.git with heimdal-1.2.x releases. These ones are already usable and hopefully soon in tree.