Hi! Not quite sure what is the conversation here, but if you need my input, please do tell (preferrably in english - or point me to the essential bits and can try machine-translate it)
Hi there @jonas, the subject of the conversation was about an issue we have for the gcli command line application.
That application is built as a
-
Linux binaries (amd64 + arm64), as well as Debian
.debpackage files. -
MacOS binary plus
homebrewequivalent of a package.
And for both Debian and Homebrew it seems the gcli name is already taken by other official packages.
So this post is about two things:
-
Coming up with a new name for the
gcliapplication, that would be unique and not conflict with existing packages inDebianandHomebrew. -
A request for help in properly registering the new name in both
DebianandHomebrewpackage repositories so that this issue doesn’t occur again.
And I am hoping you could help with that last point, specifically for Debian ![]()
Debian is not a registry.
Securing a namespace (i.e. name of package, command, etc.) involves maintaining a package.
I already maintain far too many packages in Debian, so I will not volunteer for new ones here (and in fact, I would prefer if someone closer to this mostly french-spanish tool would take over maintaining silkaj as well). What I can offer is to help guide you or others willing to step in themselves and take on the work and responsibility of maintaining the project as an official package in Debian.