Re: namespace conflict != package Conflict?
On Mon, Jun 13, 2005 at 09:46:27AM -0600, Sebastian Kuzminsky wrote:
> Steve Greenland <email@example.com> wrote:
> > On 12-Jun-05, 02:27 (CDT), Hamish Moffatt <firstname.lastname@example.org> wrote:
> > > >From my reading of your package description for cogito,
> > > the name GIT (the version control system) doesn't seem to
> > > mean anything in particular. So renaming it would not be a big loss.
> > The upstream name isn't going to change. There are probably already
> > more users of GIT-the-VCS than GIT-the-tools. So if you rename git for
> > Debian, we are very likely going to to be incompatible.
> > Just Conflict with the git package. The overlapping user base is likely
> > to be nil.
> There is at least one user that wants both... I got a bug report about
> this before I made cogito.deb Conflict with git.deb. (Then of course
> I was told that that was the wrong approach, so I _removed_ cogito's
> /usr/bin/git and removed the Conflict with git.deb.)
> But I agree totally with you. I'd much rather conflict with GNU
> Interactive Tools and have git-the-vcs be compatible with non-debian
> universe. That seems like the lesser of two evils. But everyone else
> on debian-devel seems to want it the other way so I gave in for now.
More importantly, the policy forbids it, as was already noted before in
this very same thread. This thread is running in circles...
I hope everything has been said by now so people can move on with the
C++ transition and such :)?
Jeroen van Wolffelaar
Jeroen@wolffelaar.nl (also for Jabber & MSN; ICQ: 33944357)