[opensuse-factory] package name conventions
Hi, I'm wondering that since some time but again found some examples where I just don't understand our current naming conventions. The examples I mean python3-mailman golang-github-prometheus-node_exporter golang-github-prometheus-prometheus I somewhat understand such a naming convention for typical modules. This is what we had since ages and it's important if a module is for python2, python3 or golang indeed. But for standalone software like mailman, prometheus-node-exporter and prometheus itself? I don't care if the thing is written in python, golang or $WHATEVER. I also do not care if it's hosted on github. Debian package names are e.g. prometheus prometheus-node-exporter So is this really a reasonable approach to package naming? Wolfgang -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Sat, Feb 22, 2020 at 5:17 PM Wolfgang Rosenauer <wolfgang@rosenauer.org> wrote:
Hi,
I'm wondering that since some time but again found some examples where I just don't understand our current naming conventions.
The examples I mean
python3-mailman golang-github-prometheus-node_exporter golang-github-prometheus-prometheus
I somewhat understand such a naming convention for typical modules. This is what we had since ages and it's important if a module is for python2, python3 or golang indeed.
But for standalone software like mailman, prometheus-node-exporter and prometheus itself?
I don't care if the thing is written in python, golang or $WHATEVER. I also do not care if it's hosted on github.
Debian package names are e.g. prometheus prometheus-node-exporter
So is this really a reasonable approach to package naming?
Standalone software does not require being named that way. I certainly didn't package Pagure that way: https://build.opensuse.org/package/show/openSUSE:Factory/pagure Fedora, Debian, and openSUSE all agree that it isn't required for that. However, some people in openSUSE *like* naming it that way, so their packages in openSUSE are named thusly. -- 真実はいつも一つ！/ Always, there's only one truth! -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
I thought the same thing for python-certbot. It's not a python module but a standalone service. That names suggests it's some sort of library or API. moozaad On Sat, 22 Feb 2020 at 22:17, Wolfgang Rosenauer <wolfgang@rosenauer.org> wrote:
Hi,
I'm wondering that since some time but again found some examples where I just don't understand our current naming conventions.
The examples I mean
python3-mailman golang-github-prometheus-node_exporter golang-github-prometheus-prometheus
I somewhat understand such a naming convention for typical modules. This is what we had since ages and it's important if a module is for python2, python3 or golang indeed.
But for standalone software like mailman, prometheus-node-exporter and prometheus itself?
I don't care if the thing is written in python, golang or $WHATEVER. I also do not care if it's hosted on github.
Debian package names are e.g. prometheus prometheus-node-exporter
So is this really a reasonable approach to package naming?
Wolfgang -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
W dniu 22.02.2020 o 23:17, Wolfgang Rosenauer pisze:
Hi,
I'm wondering that since some time but again found some examples where I just don't understand our current naming conventions.
The examples I mean
python3-mailman golang-github-prometheus-node_exporter golang-github-prometheus-prometheus
I somewhat understand such a naming convention for typical modules. This is what we had since ages and it's important if a module is for python2, python3 or golang indeed.
But for standalone software like mailman, prometheus-node-exporter and prometheus itself?
I don't care if the thing is written in python, golang or $WHATEVER. I also do not care if it's hosted on github.
Debian package names are e.g. prometheus prometheus-node-exporter
So is this really a reasonable approach to package naming?
Wolfgang
There's a rpm's feature called "Provides:". You can check what a package provides using "zypper --no-refresh info --provides package_name". In your examples python3-mailman provides mailman and golang-github-prometheus-node_exporter provides node_exporter and prometheus(node_exporter). (unfortunately golang-github-prometheus-prometheus has no extra provided names) If you for example type "sudo zypper install mailman", zypper will do the right thing and install python3-mailman. So as long as package has good "Provides", it doesn't matter if it follows any other naming convention.
Am Samstag, 22. Februar 2020, 23:55:56 CET schrieb Adam Mizerski:
So as long as package has good "Provides", it doesn't matter if it follows any other naming convention.
Well, I does matter if you run "zypper se python3" looking for python3 modules. Results get cluttered that way unnecessarily. vinz. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 23/02/2020 01.18, Vinzenz Vietzke wrote:
Am Samstag, 22. Februar 2020, 23:55:56 CET schrieb Adam Mizerski:
So as long as package has good "Provides", it doesn't matter if it follows any other naming convention.
Well, I does matter if you run "zypper se python3" looking for python3 modules. Results get cluttered that way unnecessarily.
Or if you use YaST to try find "mailman". Maybe there is a "Pascal-mailman" I would prefer instead >:-P -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
On Sat, Feb 22, Wolfgang Rosenauer wrote:
Hi,
I'm wondering that since some time but again found some examples where I just don't understand our current naming conventions.
The examples I mean
python3-mailman
That's because somebody wanted that mailman works with python2 and python3 and used the python module macros for it. In my opinion, this doesn't make any sense, it should be only "mailman" and only using python3...
golang-github-prometheus-node_exporter golang-github-prometheus-prometheus
That's coming from the old day, where go didn't had module/vendor support. The packages where named after the "import" statement to make packaging and building in OBS easier. That's not needed today anymore and not done for new packages. The content of the prometheus packages is outdated, somebody should overhaul them and rename them ... Thorsten -- Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & MicroOS SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany Managing Director: Felix Imendoerffer (HRB 36809, AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 02/22/2020 04:17 PM, Wolfgang Rosenauer wrote:
Hi,
I'm wondering that since some time but again found some examples where I just don't understand our current naming conventions.
The examples I mean
python3-mailman golang-github-prometheus-node_exporter golang-github-prometheus-prometheus
snip
So is this really a reasonable approach to package naming?
No, not unless you are packing more than one distinct and different versions of the package, one hosted on github and one not, one with golang and one with something else. Otherwise the "golang-github-" is superfluous. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (8)
-
Adam Mizerski -
Carlos E. R. -
David C. Rankin -
Jon Brightwell -
Neal Gompa -
Thorsten Kukuk -
Vinzenz Vietzke -
Wolfgang Rosenauer