Le mardi 05 juin 2012 à 16:24 +0200, Ricardo Mones a écrit : > I don't know about that git precedent.
There was an old package named git. Then a new one, more popular, originally named git-core. Now git is what people expect git to be on a Linux system. And epiphany is not. > Anyway my opinion is simple, and all > the confussion comes by the changes made in epiphany-browser package to > hijack the epiphany name, despite being already used by an existing package. No, the confusion comes from two upstream packages having the same name. > > This attitude is causing all sorts of bugs in epiphany since we have to > > rename it to “epiphany-browser” in many places. > > Since I've done several of those reassignations I don't think that's causing > much trouble to you. How much are "all sort of bugs"? Because you make it look > like you were all day long renaming bugs from epiphany... :-P Documentation pointing to a binary named epiphany, not epiphany-browser. Desktop files, documentation files, links, icons all failing to work randomly upon new upstream releases because they expect “epiphany” as name, not “epiphany-browser”. Other GNOME modules failing to find epiphany because it doesn’t have the right name. Etc. > Sure, then maybe you have a reason to revert epiphany-bin to epiphany > rename [0] which later caused http://bugs.debian.org/216489, and basically > where all the confussion comes from. Maybe you could explain your reasons to piss off users by not renaming your pet package with 0.55% popcon. > If you had choose renaming to epiphany-browser, all of this would be fine: > epiphany package would be providing epiphany binary and epiphany-browser > would be providing epiphany-browser. This is exactly what we do, yet an epiphany binary is necessary for compatibility. > But I guess it's more simple to say I'm the stubborn guy, thanks Josselin > by your great explanation of the situation. Yes, it’s a shorter but quite equivalent explanation. -- .''`. Josselin Mouette : :' : `. `' `- -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
