[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

gratuitous -dev package renaming



Can someone please explain to me why all of the gnustep -dev packages need
to have the upstream version number in their names?  The new and old -dev
packages don't seem to be API-incompatible; I've just NMUed one package that
was left uninstallable in unstable, and all it took to rebuild it was to
change the build-dependencies.  Yet there are literally dozens of packages
that have been left unbuildable for over a month since the new upstream
version of gnustep was uploaded, with no sign of activity.

Are there really differences in the new version that warrant forcing
sourceful changes in all of the reverse-dependencies?  If not, I'm inclined
to NMU gnustep-base and gnustep-gui to Provide: the old names of these -dev
packages and schedule binNMUs for the affected packages, so that this
gnustep transition doesn't continue to drag on.

-- 
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
vorlon@debian.org                                   http://www.debian.org/

Attachment: signature.asc
Description: Digital signature


Reply to: