Path: csiph.com!aioe.org!bofh.it!news.nic.it!robomod From: Ghislain Vaillant 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 00:40:01 +0100 Message-ID: References: X-Original-To: "W. Martin Borgert" X-Mailbox-Line: From debian-python-request@lists.debian.org Mon Mar 12 23:30:01 2018 Old-Return-Path: X-Amavis-Spam-Status: No, score=-7.099 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-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-ot0-x22c.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=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=hVnz9aSg5/Ag5VOLDIQnz6tMZWoywUdSkH6eaOFZYyA=; b=kQaZbk7FZynSi99B2gzuo5LgRTn6ksqXR4arcx7MEDt70wMP53x86QsrBTmQmiHq11 zt1NoTl7u5GmoW0QOxXanZqgB9gDB+N6lXiYjbFV6okqtwK1xtgp+F60rJXWmKnQuZLF WYVHmupNrS6xbFeljlU2LZpOZB3eX+1tkksNzDNY295y1mxU7gSF87y8m50+qbyrEqeA 5eezfkpKlwO7QR8kQ2P98O/DIoPOtuh8zshi+SRC5W6YWjJRI4zYHRLNiSZTxcmS9u7Q ZGPF8UqfbRsWE2Ft29cRZhRvKCr2zHTbeFus76kS7yRi9M/VT8LA/8UcaxvEeWq71pQt Mhqg== X-Google-Dkim-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=hVnz9aSg5/Ag5VOLDIQnz6tMZWoywUdSkH6eaOFZYyA=; b=tf43EB3DhWGY3caEaAtbz8xsO5/UsvrhleqYhtipP2s8ZwC9Ea1j+Ya10TtcXl7Pn+ zvlKC3WMbL2TguPi+wCHuF85c+koFCqqYx91ZbF5SUUvlzoA3/swowTIjFci14Cmpqcw uspCsnZH8etFIrNGRDt/bHdVP/OEXWDw8U15CHBRWzr/Ix3HpQ/A0V5oQX+n0Dm7pKGB vJIolsgvaOodSZMiqQRcMzos0kZU/qoXcS2qpTzAsYSh84Vd09+6UT8boOTYH5JumagE lWG6IBMBxosS3MQL+3Ox1ewidWOYbEc7pRP6+IAjcSPWU/MKTpdEXXvMPcIOLpS8RU3x 8voA== X-Gm-Message-State: AElRT7EA2AhHrWQ2uf2fQSmLqek8Xj1IK5LYvo02C50JihgcGDp46KAk EHVeclNtT88o4Bj0nc2EvdcJBtFW/oXO6xRsuAk= X-Google-SMTP-Source: AG47ELuEe8N+TyIaBXnM63/qu3orQ9nPFepz1wsCZSRaGg3vMYvci4d+zrJhkd/nXRGJ2reD49cknhHw4tGRy/enDCA= X-Received: by 10.157.36.81 with SMTP id p75mr6415261ota.318.1520897384015; Mon, 12 Mar 2018 16:29:44 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" X-Mailing-List: archive/latest/15633 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/CAFzxpWoZXmR9NwnJy+707ZK-bFQncjvu7ViYQ9JXjC3iZNsWxQ@mail.gmail.com Approved: robomod@news.nic.it Lines: 21 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Cc: Thomas Goirand , debian-python X-Original-Date: Mon, 12 Mar 2018 23:29:43 +0000 X-Original-Message-ID: X-Original-References: <20180312101616.GA21465@fama> <20180312223017.GD10894@fama> Xref: csiph.com linux.debian.maint.python:10238 2018-03-12 22:30 GMT+00:00 W. Martin Borgert : > On 2018-03-12 23:15, Thomas Goirand wrote: >> But what now that python-foo is gone? Should I rename the doc package? > > No, but that's just my gut feeling. Definitely not, indeed. The python- prefixes in python-foo and python-foo-doc are not exactly equivalent. The former usage refers to the Python 2 interpreter, the latter refers to Python *the language*. It's unfortunate our naming convention did not explicitly separate between both as Arch packages do, whereby `python` is used for source package and `python2` for binary packages targeting CPython 2.x. 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`. Ghis