On 9/1/25 07:39, Jakub Ružička wrote:
I've used nvchecker as a library, thus the package naming, but it's
primarily a CLI tool, so src:nvchecker with nvchecker package makes
sense too, possibly with
Provides: python3-nvchecker
Similarly, if src:python-nvchecker with python3-nvchecker is chosen, I
think it should
Provides: nvchecker
So that
apt-get install nvchecker
nvchecker
works as expected by users.
I agree that having two source packages is confusing and not a good
route. Aside from being the original, src:nvchecker in Unstable is
currently more up-to-date with respect to upstream than
src:python-nvchecker.
There is also an option to have the python module in python3-nvchecker and
nvchecker minimal package only containing the executable nvchecker
script with dependency on python3-nvchecker.
I didn't find definitive answer on this.
I have done this before, but within a single source package if there is
a potential need for just the library, so I think this is a good option.
To do this within src:nvchecker, I think we would need to request that
src:python-nvchecker be removed from Unstable, and then set up the
binary package python3-nvchecker in src:nvchecker to take all the files
except /usr/bin/nvchecker.
thanks and regards
Afif
--
Afif Elghraoui | عفيف الغراوي
https://afif.ghraoui.name
