Sorry about the bug mis-identification (I knew better). On Jun 18, 2014, at 11:58 AM, Piotr Ożarowski wrote:
>> However, in almost all such cases, the binary package will Depend:
>> ${python3:Depends} so that should be a good enough indication that
>> the binary package should get those transformations.
>
>I will do something like this (checking for ${python3:Depends} or
>${python:Depends} or ${pypy:Depends} in Depends) in foo packages, not in
>python-foo ones
I think this is fine, however we do need to be more explicit about cases where
a package is either split into bilingual libraries + executable, or just an
application with ancillary libraries (some might say "private" library).
There are lots of examples where the latter exists in python-foo binary
packages. virtualenv was a prime example and its Python 3 executable has now
been moved to `virtualenv` (no prefix). If we cannot have a Python 3
application live in a python-foo binary package, then we need to be explicit
about this in Python policy, and the application style guide.
signature.asc
Description: PGP signature
