Bug#493951: libpkg-guide: recommendations are contrary to accepted best practices
tags 493951 +help thanks On Wed, Aug 6, 2008 at 07:32, Steve Langasek vor...@debian.org wrote: Package: libpkg-guide Version: 0.0.20070413 Severity: serious The libpkg-guide that has been packaged and is now in the archive gives recommendations regarding -dev package naming which are not at all representative of a consensus in Debian. We already have problems with library maintainers inserting sonames into their -dev package names based on the unclear/misguided advice of this document; shipping it in a stable release would be seen by many as an endorsement by the Debian project, and no such endorsement exists. There *particularly* isn't such an endorsement from the Debian release team, for whom gratuitous -dev package name changes make library transitions more difficult by orders of magnitude. This package should not be included in a stable release until the recommendations have been revised to reflect best practices. I waited long, then I finally decided to ask for help to fix this bug. Sadly, I don't have the time to properly read all the documentation and forge a patch to the current package (and Junichi is in the same situation). So I'm here to ask for your help in fixing it. Thanks in advance, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#493951: libpkg-guide: recommendations are contrary to accepted best practices
Hi Steve, thanks for taking care The libpkg-guide that has been packaged and is now in the archive gives recommendations regarding -dev package naming which are not at all representative of a consensus in Debian. We already have problems with library maintainers inserting sonames into their -dev package names based on the unclear/misguided advice of this document; shipping it in a stable release would be seen by many as an endorsement by the Debian project, and no such endorsement exists. There *particularly* isn't such an endorsement from the Debian release team, for whom gratuitous -dev package name changes make library transitions more difficult by orders of magnitude. May I kindly ask you if you're willing to provide a patch against libpkg-guide (the code is in git[1])? Alternatively, may you please give us some hints about where thinks have to be fixed (I supposed you read recently the doc so it's fresh :) ) and references for what Debian recommends for -dev package? Thanks in Advance, Sandro [1] git://git.debian.org/git/collab-maint/libpkg-guide.git -- Sandro Tosi (aka morph, Morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#493951: libpkg-guide: recommendations are contrary to accepted best practices
Package: libpkg-guide Version: 0.0.20070413 Severity: serious The libpkg-guide that has been packaged and is now in the archive gives recommendations regarding -dev package naming which are not at all representative of a consensus in Debian. We already have problems with library maintainers inserting sonames into their -dev package names based on the unclear/misguided advice of this document; shipping it in a stable release would be seen by many as an endorsement by the Debian project, and no such endorsement exists. There *particularly* isn't such an endorsement from the Debian release team, for whom gratuitous -dev package name changes make library transitions more difficult by orders of magnitude. This package should not be included in a stable release until the recommendations have been revised to reflect best practices. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ [EMAIL PROTECTED] [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
