Groups > linux.debian.maint.python > #10243

Re: Where to put docs of a -doc package for python 2 + 3 modules?

From	Ole Streicher <olebole@debian.org>
Newsgroups	linux.debian.maint.python
Subject	Re: Where to put docs of a -doc package for python 2 + 3 modules?
Date	2018-03-13 10:30 +0100
Message-ID	<vsOpP-3Ur-1@gated-at.bofh.it> (permalink)
References	<vssIG-6zE-9@gated-at.bofh.it> <vsDXs-5jQ-11@gated-at.bofh.it> <vsEgN-5uV-5@gated-at.bofh.it> <vsFcR-6ah-1@gated-at.bofh.it> <vsNk6-3eq-5@gated-at.bofh.it>
Organization	The Borribles

Show all headers | View raw

Thomas Goirand <zigo@debian.org> writes:
> On 03/13/2018 12:29 AM, Ghislain Vaillant wrote:
>> Imo, we should just make it clear in policy that source packages
>> should be named `foo` or `python-foo`,
>> and corresponding doc packages should be named `foo-doc` or `python-foo-doc`.
>
> Very often, "foo" is already taken by another package, and we have to
> fallback to python-foo. Think about generic libs for compression,
> images, network standards...
>
> Which is why I think we should have standardize on python-foo for the
> source package (which is what I do).

I disagree. Often packages already signalize their Python origin:
astropy, sunpy, pyephem etc. Or relate to pytest (pytest-mpl for
example). Or provide a Python package just as one of many other packages
(plplot). Prefixing them with "python-" increases useless redundancy,
and makes it harder for external people to find the package.

I would deviate from the rule of thumb "stick with the upstream name
unless there is a (potential) conflict". And if there is a conflict,
talk to upstream to find a solution -- it is quite probable that it will
lead to file conflicts as well (tools/apps in /usr/bin).

Best

Ole

Thread

Where to put docs of a -doc package for python 2 + 3 modules? "W. Martin Borgert" <debacle@debian.org> - 2018-03-12 11:20 +0100
  Re: Where to put docs of a -doc package for python 2 + 3 modules? Simon McVittie <smcv@debian.org> - 2018-03-12 11:40 +0100
    Re: Where to put docs of a -doc package for python 2 + 3 modules? "W. Martin Borgert" <debacle@debian.org> - 2018-03-12 14:30 +0100
  Re: Where to put docs of a -doc package for python 2 + 3 modules? Thomas Goirand <zigo@debian.org> - 2018-03-12 23:20 +0100
    Re: Where to put docs of a -doc package for python 2 + 3 modules? "W. Martin Borgert" <debacle@debian.org> - 2018-03-12 23:40 +0100
      Re: Where to put docs of a -doc package for python 2 + 3 modules? Ghislain Vaillant <ghisvail@gmail.com> - 2018-03-13 00:40 +0100
        Re: Where to put docs of a -doc package for python 2 + 3 modules? Ben Finney <bignose@debian.org> - 2018-03-13 08:20 +0100
        Re: Where to put docs of a -doc package for python 2 + 3 modules? Thomas Goirand <zigo@debian.org> - 2018-03-13 09:20 +0100
          Re: Where to put docs of a -doc package for python 2 + 3 modules? Ghislain Vaillant <ghisvail@gmail.com> - 2018-03-13 10:00 +0100
          Re: Where to put docs of a -doc package for python 2 + 3 modules? "W. Martin Borgert" <debacle@debian.org> - 2018-03-13 10:00 +0100
          Re: Where to put docs of a -doc package for python 2 + 3 modules? Ole Streicher <olebole@debian.org> - 2018-03-13 10:30 +0100
            Re: Where to put docs of a -doc package for python 2 + 3 modules? Thomas Goirand <zigo@debian.org> - 2018-03-13 14:10 +0100

csiph-web