On Sun, Oct 24, 1999 at 06:28:43PM +0200, Niels Möller wrote: > I'm aware of the conflict. > > I think this description misses the problem by quite some distance. > It's not the name of the *package* that creates problems for you (I > have suggested using the name "lsh-utils" or some such for the > package, which as far as I know should solve this aspect of the > conflict in a reasonable way). The problem is the *filename* of one of > the installed program, "lsh". Note that lsh-the-free-ssh includes > several programs: A client, a server and a handful other utilities. > > If I'm allowed to give a short rant, I think it is really bad that [rant cut -- and the merits not discussed] > An even easier partial solution is to simply mark the "lsh" (dos-like > shell) as conflicting with "lsh-utils" (ssh-like stuff). But IIRC that > was rejected because conflicting meanings of the name "/usr/bin/lsh" > was against debian policy. > Sorry to butt in... From what I read in the original email... it is a package name problem, not just a binary name conflict. Take two users, Person A and Person B. Person A has chosen the dos like lsh shell as his prefered shell, he's used for years and he's getting ready to customize a debian box for his use. Take Person B. He's never even heard of the lsh shell (I hadn't until this topic came up a week ago) but he *has* heard of the ssh free replacement lsh and want's to give it a try... Both people do "apt-get install lsh".. what happens? Either Person A or Person B will be surprised... I don't think the original message even got to addressing binary namespace conflicts... -- Please cc all mailing list replies to me, also. ========================================================================= * http://benham.net/index.html <gecko@benham.net> <>< * * -------------------- * -----------------------------------------------* * Debian Developer, Debian Project Secretary, Debian Webmaster * * <gecko@debian.org> <secretary@debian.org> <lintian-maint@debian.org> * * <webmaster@debian.org> <gecko@fortunet.com> <webmaster@spi-inc.org> * =========================================================================
Attachment:
pgpOeaNBEZl3Y.pgp
Description: PGP signature