[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

rstcheck: how should I package the new public module?



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 │
⠈⠳⣄⠀⠀⠀⠀   ╰────────────────────────────────────────────────────╯

Attachment: signature.asc
Description: PGP signature


Reply to: