Hi,

rstcheck used to be a pure CLI application, so I packaged it as
"rstcheck" with a private module in /usr/share/rstcheck. The latest
version has added a public module interface, so "import rstcheck"
has become a thing and the module needs to be installed publicly for
that.

My question is: should I move/rename the whole package to
python3-rstcheck (and keep rstcheck temporarily as transitional
dummy package), or should I keep /usr/bin/rstcheck in the old
package indefinitely and only move the module to python3-rstcheck?

The latter solution feels cleaner to me, because it neatly separates
the library and the appliation, but at the cost of an almost empty
binary package, which is frowned upon by the FTP team. Any
suggestions how I should proceed?


Cheers
Timo

--
⢀⣴⠾⠻⢶⣦⠀ ╭────────────────────────────────────────────────────╮
⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling │
⢿⡄⠘⠷⠚⠋⠀ │ 9B03 EBB9 8300 DF97 C2B1 23BF CC8C 6BDD 1403 F4CA │
⠈⠳⣄⠀⠀⠀⠀ ╰────────────────────────────────────────────────────╯

-----BEGIN PGP SIGNATURE-----

iQGzBAABCgAdFiEEJvtDgpxjkjCIVtam+C8H+466LVkFAmJdnL8ACgkQ+C8H+466 LVkdaAv+NJol6xtoBj609DsNwc0AIRYRVYmnc7MZ60iAMR2s45uHdAM7n5StKAS5 98KIZ6h8NGaa/qEJQ8QxW5kIsb3rVp3IhW96WtGbWONBneMSAvjdBPBogh4jA+kz tGCmbwlzPH1UwhyHzeUcqLsgCD5jnjdjQD6LwtqDiecwU0l9qtIFxzcu1jYf/d79 +pxVVTFvmlLXi8IKXq/x4Up3UOuE0Cwb950ljRgiz8Es2PER4q+ySN22x8qWRYz0 PhiZr+iqjoJn5t7rWeMNzmU/FsFT+dkeBJeJr1CpLAfKXQMoyh4Ecz0yJm9dwvDO PpPspg+jrwhvqPNbjFnrdYYr8+7isyFmZAXlYZozTMh

On Mon, Apr 18, 2022 at 07:15:46PM +0200, Timo R�hling wrote:

Hi,

rstcheck used to be a pure CLI application, so I packaged it as
"rstcheck" with a private module in /usr/share/rstcheck. The latest
version has added a public module interface, so "import rstcheck"
has become a thing and the module needs to be installed publicly for
that.

My question is: should I move/rename the whole package to
python3-rstcheck (and keep rstcheck temporarily as transitional
dummy package), or should I keep /usr/bin/rstcheck in the old
package indefinitely and only move the module to python3-rstcheck?

The latter solution feels cleaner to me, because it neatly separates
the library and the appliation, but at the cost of an almost empty
binary package, which is frowned upon by the FTP team. Any
suggestions how I should proceed?

Hi Tim,

We've done exactly that with spyder: spyder contains just the binary,
manpage, desktop file, appdata, icon and reportbug file. This is also
helpful if there is ever a Python 4.x, as then there will be four
packages: rstcheck, python3-rstcheck and python4-rstcheck.

This information may be of use to you.

Best wishes,

Julian

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)