Matthew Wilcox <[EMAIL PROTECTED]> quoted from policy: > Two different packages must not install programs with different > functionality but with the same filenames. (The case of two programs > having the same functionality but different implementations is handled via > "alternatives" or [...]
I think that policy is not violated: The git installed by cogito*deb is a version control system. The git installed by git*deb is a shell script which calls the same version control system if called non-interactively. The two programs have the same functionality, but git*deb's offers more functionality if called interactively. I'm sure most people can think of alternatives where one implementation offers a superset of the other. > The maintainers should report this to the debian-devel mailing > list and try to find a consensus about which program will have to be > renamed. If a consensus cannot be reached, both programs must be renamed. This was reported to debian-devel by Sebastian Kuzminsky on 2005-08-11. Consensus seemed to be for the package maintainers to work it out and this is what they chose. If you want to reopen that discussion, please raise it on debian-devel again and cc this bug and the cogito package maintainer. As I understand it, git*deb's git will be renamed upstream to gitfm, matching git*deb, but it is desirable to provide a nice transition for sarge users, so git*deb's git inherits cogito*deb's git's functionality for now if available. What better solution do you suggest? -- MJR/slef Laux nur mia opinio: vidu http://people.debian.org/~mjr/ Bv sekvu http://www.uk.debian.org/MailingLists/#codeofconduct -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
