On Thu, Mar 22, 2007 at 07:50:35PM +0100, Josselin Mouette wrote: > Le jeudi 22 mars 2007 à 14:50 +0100, Pierre Habouzit a écrit : > > exactly, putting current is just yet-another-place where the > > maintainers declares that he will only prepare the package for "current" > > python. And you're right, python-(all-?)-dev is a already here to give a > > hint to the dh_tool about your intention. Excellent point. > > Just nitpicking: the dh_ tool doesn't need to know that, as it can guess > it from what was previously built. This is a hint for the release > managers (to know which packages need a binNMU), and could be the base > for a script automating the build process. It's not necessarily true: when there is only one python supported, you can't tell the difference between a package that only supports the default python, or any of them :) And the maintainer can change his mind too, so looking in the past packages looks brittle. -- ·O· Pierre Habouzit ··O madcoder@debian.org OOO http://www.madism.org
Attachment:
pgpdSfUvex2ML.pgp
Description: PGP signature