Ok, I see.. So in this case I think the name should be
"python3-gbinder-python", perhaps a bit complex but clearly identifies
python release and real name of the project.
Cheers
El 2024-01-15 11:17, Arnaud via SlackBuilds-users va escriure:
Hi all.
I've created a slackbuild for gbinder-python (
https://github.com/waydroid/gbinder-python ) but I''ve doubts about
how
shall be the package named: python3-gbinder as usual with python
modules
or gbinder-python as the real name of the project?
Thx in advance,
--
=== In soft we trust ===
You can look on repology here :
https://repology.org/projects/?search=gbinder
Clicking on the * next to gbinder-python shows that :
https://repology.org/project/gbinder-python/related
Where you can see that this package has different names, and that's
fine.
So python3-gbinder or even python3-gbinder-python both looks OK.
gbinder-python doesn't specify which python, and the decision has been
to
prefix python packages with python2/3.
I say that because sometime it's not that easy, for exemple for
python3-python-editor, I need that name, because python-editor
and editor are two different projects, so we could have a
python3-editor and a python3-python-editor.
And, well, repology is not a reference, but it's useful, or at least
practical, to be properly referenced there.
- Yth.
_______________________________________________
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/
--
=== In soft we trust ===
_______________________________________________
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/
