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

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

Path	csiph.com!goblin1!goblin.stu.neva.ru!news2.arglkargh.de!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod
From	Ghislain Vaillant <ghisvail@gmail.com>
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:00:02 +0100
Message-ID	<vsNWO-3uC-17@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>
X-Mailbox-Line	From debian-python-request@lists.debian.org Tue Mar 13 08:51:20 2018
Old-Return-Path	<ghisvail@gmail.com>
X-Amavis-Spam-Status	No, score=-6.999 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FOURLA=0.1, FREEMAIL_FROM=0.001, LDO_WHITELIST=-5, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
X-Policyd-Weight	NOT_IN_SBL_XBL_SPAMHAUS=-1.5 NOT_IN_BL_NJABL=-1.5 CL_IP_EQ_HELO_IP=-2 (check from: .gmail. - helo: .mail-wr0-x236.google. - helo-domain: .google.) FROM/MX_MATCHES_HELO(DOMAIN)=-2; rate: -7
Dkim-Signature	v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=message-id:subject:from:to:date:in-reply-to:references:mime-version :content-transfer-encoding; bh=uxSV+SDX9DJUAihEojHGXIG2wipzTFTqTE4MSEzt95g=; b=GOTlPZukTB8mmpzHV5Z6oUiStOHy7LMRlApNBEr0FytJcrVmChzlennI+Y70OF0t/N iCc44l8+o/4k697i6Zd9hx1HH6YEpNUIKlr06oubHLPLxOipgrA32a7p5aMqA71OpxLF igVdWc095waYmuTXiSxUXJzEJ8qD4ZVdATSfXv8fmg8F96wIzPTtiRxb4Pq2FFZdUPfG j7gowGzyJr/GqYlw1u1HpUVoIC88dCKKhqMZNBCgj/CAZG/G8s1lpweW0wo5bXOtLMLI qB7B0acYai91jRYNvIAb8t8qxytPZiQjVohdYxykzllL25/tvrpOESnqB3Sx1WjZv/jI /qPA==
X-Google-Dkim-Signature	v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:date:in-reply-to :references:mime-version:content-transfer-encoding; bh=uxSV+SDX9DJUAihEojHGXIG2wipzTFTqTE4MSEzt95g=; b=R+CRYlF7Lz3+Kz+hdZ9+Up1nDnOk+TN2EZK4py7v+d6T2moDKp9A+p83V4mCkNBoZ2 lSVgVc98X29luXOVhruKPY4KAYfkyb7yITqgG3qvgHSAr2sMkPE2An08hvafvAGk7HFl vGIMcMbL8hfg4qi9DJjc7ZSP5lL8KEtgXinG7BN0H0XmsTJNrcSmV7G53R2pinkIUxlp RiVYmHSyAEgKKATf4mcAHYSF3rXc1QbCatepbRPIOiR+IR1VNn9U2U6oREflG6bWXIKq OojbEHbptZMubpvlgqZ8+itl+GwY2sfX5FV8rHgWM5TMsnKsFLX8yPOG7oS7tpopDt80 tLmw==
X-Gm-Message-State	AElRT7Gg6px0DhIz6uNcb93cnyNgwJUSbCet/erbgVepPeitpNe5c/lY y5q4ahrsCx/kz8QHR6OQWiFS4R0d
X-Google-SMTP-Source	AG47ELu093brBf5ltDaQ6VaCpKbtKs4diRqeSdPwDLWN1x5xDfGyeDJSHOKh3zogB600G/hpEth4xw==
X-Received	by 10.28.138.143 with SMTP id m137mr5339811wmd.85.1520931064018; Tue, 13 Mar 2018 01:51:04 -0700 (PDT)
Content-Type	text/plain; charset="UTF-8"
X-Mailer	Evolution 3.26.5-1
MIME-Version	1.0
Content-Transfer-Encoding	8bit
X-Mailing-List	<debian-python@lists.debian.org> archive/latest/15636
List-ID	<debian-python.lists.debian.org>
List-URL	<https://lists.debian.org/debian-python/>
List-Archive	https://lists.debian.org/msgid-search/1520931061.2209.27.camel@gmail.com
Approved	robomod@news.nic.it
Lines	22
Organization	linux.* mail to news gateway
Sender	robomod@news.nic.it
X-Original-Date	Tue, 13 Mar 2018 08:51:01 +0000
X-Original-Message-ID	<1520931061.2209.27.camel@gmail.com>
X-Original-References	<20180312101616.GA21465@fama> <f2135e53-305c-665d-a02d-1b1e2ac02eab@debian.org> <20180312223017.GD10894@fama> <CAFzxpWoZXmR9NwnJy+707ZK-bFQncjvu7ViYQ9JXjC3iZNsWxQ@mail.gmail.com> <b294c451-c7c0-0ddc-cd30-90ee63791ad7@debian.org>
Xref	csiph.com linux.debian.maint.python:10241

Show key headers only | View raw

Le mardi 13 mars 2018 à 09:18 +0100, Thomas Goirand a écrit :
> 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...

Agreed.

> Which is why I think we should have standardize on python-foo for the
> source package (which is what I do).

Same here.

Do you think we should be recommending the use of `python-foo` in the
DPMT packaging policy? This could help avoiding ITPs for `python3-bar`.

Ghis

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