Path: csiph.com!news.redatomik.org!aioe.org!bofh.it!news.nic.it!robomod From: Ole Streicher Newsgroups: linux.debian.maint.python Subject: Re: Where to put docs of a -doc package for python 2 + 3 modules? Date: Tue, 13 Mar 2018 10:30:01 +0100 Message-ID: References: X-Mailbox-Line: From debian-python-request@lists.debian.org Tue Mar 13 09:27:10 2018 Old-Return-Path: X-Amavis-Spam-Status: No, score=-6.751 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, HEADER_FROM_DIFFERENT_DOMAINS=0.249, LDO_WHITELIST=-5] autolearn=ham autolearn_force=no X-Policyd-Weight: using cached result; rate: -7 Organization: The Borribles User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Lines: 27 X-Mailing-List: archive/latest/15638 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/ytzina0nxuv.fsf@news.ole.ath.cx Approved: robomod@news.nic.it Sender: robomod@news.nic.it X-Original-Date: Tue, 13 Mar 2018 10:11:52 +0100 X-Original-Message-ID: X-Original-References: <20180312101616.GA21465@fama> <20180312223017.GD10894@fama> Xref: csiph.com linux.debian.maint.python:10243 Thomas Goirand 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