Groups > linux.debian.maint.python > #13644 > unrolled thread

Sphinx theme package naming conventions

Started by	Andrius Merkys <merkys@debian.org>
First post	2021-10-21 09:30 +0200
Last post	2021-10-21 13:50 +0200
Articles	3 — 2 participants

Back to article view | Back to linux.debian.maint.python

  Sphinx theme package naming conventions Andrius Merkys <merkys@debian.org> - 2021-10-21 09:30 +0200
    Re: Sphinx theme package naming conventions Dmitry Shachnev <mitya57@debian.org> - 2021-10-21 13:40 +0200
      Re: Sphinx theme package naming conventions Andrius Merkys <merkys@debian.org> - 2021-10-21 13:50 +0200

#13644 — Sphinx theme package naming conventions

From	Andrius Merkys <merkys@debian.org>
Date	2021-10-21 09:30 +0200
Subject	Sphinx theme package naming conventions
Message-ID	<DaAGu-7v3-1@gated-at.bofh.it>

Hello,

I am working to package sphinx_press_theme (ITP bug #996543). According
to Python package naming conventions [1] proper binary package name for
it would be python3-sphinx-press-theme. However, most of sphinx theme
packages seem to be named $THEME_NAME-sphinx-theme (source package),
resulting in names like python3-$THEME_NAME-sphinx-theme (binary
package) [2].

Is it OK to follow [1] and stay faithful to upstream name, or should I
rename both source and binary packages to match already existing sphinx
theme package names?

[1]
https://www.debian.org/doc/packaging-manuals/python-policy/index.html#module-package-names
[2]
https://packages.debian.org/search?suite=sid&section=all&arch=any&searchon=sourcenames&keywords=sphinx

Best,
Andrius

[toc] | [next] | [standalone]

#13645

From	Dmitry Shachnev <mitya57@debian.org>
Date	2021-10-21 13:40 +0200
Message-ID	<DaEAp-1kk-5@gated-at.bofh.it>
In reply to	#13644

[Multipart message — attachments visible in raw view] — view raw

Hi Andrius!

On Thu, Oct 21, 2021 at 10:26:53AM +0300, Andrius Merkys wrote:
> Hello,
>
> I am working to package sphinx_press_theme (ITP bug #996543). According
> to Python package naming conventions [1] proper binary package name for
> it would be python3-sphinx-press-theme. However, most of sphinx theme
> packages seem to be named $THEME_NAME-sphinx-theme (source package),
> resulting in names like python3-$THEME_NAME-sphinx-theme (binary
> package) [2].
>
> Is it OK to follow [1] and stay faithful to upstream name, or should I
> rename both source and binary packages to match already existing sphinx
> theme package names?

I would follow the naming policy and use python3-sphinx-press-theme.

--
Dmitry Shachnev

[toc] | [prev] | [next] | [standalone]

#13646

From	Andrius Merkys <merkys@debian.org>
Date	2021-10-21 13:50 +0200
Message-ID	<DaEK6-1ns-9@gated-at.bofh.it>
In reply to	#13645

Hi Dmitry,

On 2021-10-21 14:38, Dmitry Shachnev wrote:
> On Thu, Oct 21, 2021 at 10:26:53AM +0300, Andrius Merkys wrote:
>> Is it OK to follow [1] and stay faithful to upstream name, or should I
>> rename both source and binary packages to match already existing sphinx
>> theme package names?
> I would follow the naming policy and use python3-sphinx-press-theme.

Thanks for suggestion!

Best,
Andrius

[toc] | [prev] | [standalone]

csiph-web

Sphinx theme package naming conventions

Contents

#13644 — Sphinx theme package naming conventions

#13645

#13646