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