* Leandro Doctors <ldoct...@gmail.com> [090917 10:41]: > 2009/9/17 Marvin Renich <m...@renich.org>: > > But, if I were a gnuit user and not a git-core user, I would find it > > annoying (and possibly confusing) when upgrading from lenny to squeeze > > to have a new package added that I didn't want and that is completely > > unrelated to anything I had already installed simply because a more > > popular package wanted to take over the name of a different package that > > I was using. > Perhaps including the version in the dependency helps? > > After all: > if version(git) <= LENNY_GIT_VERSION --> git == "GNU Interactive Tools" > if version(git) > LENNY_GIT_VERSION --> git == "Git Version Control > System and Friends" > > Right? > > L > (IANADD)
Adding the version to which dependency? How does that prevent git(lenny) being upgraded to git(squeeze)? gnuit already Conflicts and Replaces git (< 4.9.2-1). It also Provides git. This Provides should, I believe, be removed for either squeeze or squeeze+1. But there is a dummy (real) package git 4.9.4-1 in lenny. If aptitude (and other package managers) remove git automatically when upgrading from etch to lenny, then my objection is void, since lenny users will not have git installed unless they explicitly installed the dummy package. But if the upgrade causes both git 4.9.4-1 and gnuit 4.9.4-1 to be installed, then squeeze gnuit should conflict and replace git (< 4.9.5) so that anyone upgrading to squeeze will have git removed automatically, and the upgrade to squeeze+1 will not bring in git(-core) gratuitously. ...Marvin -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
