-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2011-05-13 00:06, Colin Watson wrote: > On Thu, May 12, 2011 at 11:45:03PM +0200, Niels Thykier wrote: >> On 2011-05-12 23:00, Colin Watson wrote: >>> Hmm. I kicked this around with some of my team. Here are a few >>> alternatives, all a bit grotty in one way or another: >>> >>> * Split lintian into two binary packages, one of which only supports >>> checking binary packages, and the other of which (still called >>> 'lintian') supports everything and depends on the first. >>> >>> * Reimplement the small number of checks we consider for this use case >>> in aptdaemon or somewhere else. >>> >>> * Split out dpkg-source from dpkg-dev. >> >> An alternative to this is to use libdpkg-perl to do the unpacking; that >> would save some depends of dpkg-dev, assuming the libdpkg-perl API is >> stable here. > > While I agree that this is a further interesting alternative over and > above those I listed, /usr/share/doc/libdpkg-perl/README.api says: > > What: libdpkg-perl (perl modules) > Status: stable > Description: > Among the perl modules provided by libdpkg-perl, you can safely rely on > those that have $VERSION set to 1.00 (or higher). Note however that the > API is defined by what's documented in the corresponding manual pages and > nothing more. You can't assume anything else based on what you read in > the source code. If you feel the need for further refinements in the > documented API, don't hesitate to file a wishlist bug against > libdpkg-perl. > . > In case of API-breaking changes, the major number in $VERSION will be > increased. For API extensions, the minor number will be increased. > > The necessary module is /usr/share/perl5/Dpkg/Source/Package.pm, which > has $VERSION set to 0.01 and has no manual page, so according to the > documentation we are not allowed to rely on that being stable yet. >
I had a short chat with Raphaël Hertzog (buxy) in #debian-qa about this and he said that the unpacking part of the module was rather stable and "it's certainly ok as a fallback when dpkg-source is not there". So as long as we only need dpkg-source -x (and not dpkg-source -b) we can use libdpkg-perl. ~Niels For reference, the entire chat: (11:01:53) nthykier: buxy: Hey, how stable is the API behind libdpkg-perl Dpkg::Source::Package? I understand it is not officially stable, but how far away is it from being stable? (11:02:18) nthykier: The context being #626476 (11:11:45) buxy: nthykier: quite far in general, as dpkg-source does much things that are not done in the perl modules, but the part that deals with unpacking is rather stable, it's certainly ok as a fallback when dpkg-source is not there (11:12:11) buxy: (i.e. my first remark applies mainly to dpkg-source -b and not dpkg-source -x) (11:12:51) nthykier: Thanks, I will try to setup Lintian with a libdpkg-perl fall-back then -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBCAAGBQJNzPeEAAoJEAVLu599gGRCE2YQAJLmuGQTGqaNkMZMLHjrO2lN vod25s54Nz/iwnW/KN2gzTR4BlTbVjhYHQGZK3tA0QJR0PfJmTD6tPTmTFzv7TI/ ZhH68x2h+ZcfncnQa9vWZBsw+A3egM0/UULhBzs03cQRTXu49OK2wxB/N2Dg9Zqc enAskxsVPeZmUtazfzAo6DV2GtH9k4EfbAMIqGJccIR8JjvK8+Z8CxFst1sqWtjH 7GkFm1+hJW8i5MmU68PbdX8BGRN2YRaRGrmDj+zNtmCS1O9aiCUB1mdALd5KJm9+ p7VsDboqDUuEsPuDYE+BDrwwQYxSNAOApU4k0I/+y171JC5PIhDUpCfxQNDBuSe7 Yfek0SMqm+Ey/9paMMeBlV06XnFditUwXSRZLPwzsP+XQ5Aw/gJPLVtAWDxqKWBc nEvkYQCvvRMDnu90sps3yuvpy1NJ2/MhU5G2qNTbBmyzvZaMY5ck0JA1uSrbciMl zcBP695XIG3jhldUgGfbPjDP62uUuioYIP9hfVRy6UyfyCsJ3Auw7JyTfNL625ey r2lxMqUv6ZJOuMB3qQta5Hvgi+E4MipBJWw7T4svlx709/KNleSzZdZdcRs6yxLY duHG9El384S6rkAjM2mIMBm34jNP1HXYYKSzTFUfVSqH19WEAvgrtMXg9q+eeJmD EJvxWDxaspFCPqbV5VGN =KPwT -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
