[Scott Kitterman, 2010-06-23] > 3. Create a new field, X-Python-Version: for Python3 versions. This avoids > concerns about control file bloat, but may be a bit confusing in combination > with the existing XS/B-P-V.
+ "Please note the lack of XB-Python-Version, i.e. X-Python-Version will be used to feed build tools only." > 4. Create a new field, X-Python3-Version: for Python3 versions and in > Squueze > +1 migrate the existing XS/B-P-V to X-Python-Version. This avoids confusion, > but does require lots of packages to be changed and tools to be updated to > recognize X-Python-Version. In the long run, it does stop Python packages > from exposing information externally that has turned out not to be very > useful. is it worth mentioning migration of XS-Python-Version to X-Python-Version? Will we ever do that? For what gain? -- Piotr Ożarowski Debian GNU/Linux Developer www.ozarowski.pl www.griffith.cc www.debian.org GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645
signature.asc
Description: Digital signature
