Hi,
On Thu, Jan 18, 2024 at 02:35:40PM +0000, Aidan wrote:
> I am looking for a sponsor for my package "dpkg-buildenv":
Similar to my recent "veto" of apt-verify in #1059267, which was
subsequently ignored and pushed into the archive anyhow, I would
like to call into question the naming of the package/application…
There are various "dpkg-build*" tools already that grabbing 'env' feels
wrong (I would confuse it probably with 'flag' on a bad day), especially
if that isn't at least discussed with dpkg maintainers (I at least see
no mention of it on the list) and given that this is something that
"just" works with Docker.
As explained in the other bug, there is no veto and as you can see its
easy to completely ignore me (and anyone else) but I wanted to say it
anyhow, so that nobody is surprised later on.
Best regards
David Kalnischkies
Thanks for taking a look David.
For the name I choose "dpkg'' because it stands for "debian package" and dpkg-buildenv is intrinsically related to debian packaging.
However I understand the usage of dpkg may imply the package has been officially created and maintained by the dpkg developers.
If the package's name was the last blocking issue preventing adoption in Debian then I would spend the time to rename it.