Ben Finney ha scritto: >> * I: Place Python applications in private directory > > What would be the test for these cases? That is, what would Lintian > actually check in the package to determine whether these should be > emitted?
This is quite complex to say, I initially thought of checking for files under /usr/bin and related modules under /usr/share/pyshared, but there are some cases where this is not enough. >> * W: Arch: all package but build-dependency on python*-dev > > Is there a converse for this, for ‘Architecture: any’ packages? Do you mean the case where there are Arch: any packages with Python scripts that requires no compilation? That's very hard to tell, and it will probably result in many false positives, so I'd check for the "all" case only. >> * I: python-support and XB-Python-Version field > > As I understand it, many people are dealing with the lack of clear > policy in this matter by having *both* ‘debian/pyversions’ file and the > ‘XB-Python-Version’ field. > > Until there is clear consensus that ‘XB-Python-Version’ is *not* > required, I would not want Lintian to check this. You was probably referring to XS-Python-Version field, while I was referring to XB-P-V. It is currently unmanaged by python-support, so I think a notice to maintainers about this could be interesting. I don't dare to touch XS-P-V or pyversions at all, given that there are several implications for those files. -- .''`. : :' : Luca Falavigna <dktrkr...@debian.org> `. `' `-
signature.asc
Description: OpenPGP digital signature
