https://bugzilla.redhat.com/show_bug.cgi?id=2040624
--- Comment #8 from Kalev Lember <klember(a)redhat.com> ---
(In reply to Ben Beasley from comment #6)
(In reply to Kalev Lember from comment #5)
> I would simplify this a bit and call the package just 'psautohint' and not
> python-psautohint because it's just an executable and not a python library.
> See
>
https://docs.fedoraproject.org/en-US/packaging-guidelines/Python/
> #_application_naming
This is a fair point. There actually is a usable Python API, e.g. [1], but
there is a good argument that the package exists primarily to provide the
executable. I think I would find it acceptable either way, but lean toward
application naming.
[1]
https://github.com/adobe-type-tools/psautohint/blob/
0a1e514a3cb86c6593e4f05814d70afc390f7e69/python/psautohint/__init__.py
Oh, that's true, and it's actually installed as well, I think -- I totally
missed it at first because the python library must be hidden behind %files -n
python3-psautohint -f %{pyproject_files} and not explicitly listed in %files.
Anyway, maybe in that case it would make sense to have a split where:
Source package name: psautohint
Two binary packages:
psautohint (/usr/bin/*)
python3-psautohint (python library)
--
You are receiving this mail because:
You are always notified about changes to this product and component
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2040624