Re: Bug#1061111: RFS: dpkg-buildenv/1.0.0 [ITP] -- Builds debian packages in a docker container.

David Kalnischkies <[email protected]>
Newsgroups gmane.linux.debian.devel.dpkg.general
Message-ID <e6jgyeozagwksrmoc5hbsp52jufxj63ixtmjpk5d5z27ibunkx@2mtu4eqb2yf3>
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
signature.asc (application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEE5sn+Q4uCja/tn0GrMRvlz3HQeIMFAmWpbh4ACgkQMRvlz3HQ
eIOlthAAp+sPHQS19W2AA3IqG1MtkqZOmBoA4rm48OXFU7W8+AAufQjHWs2+Tvk3
+x9N1WX5/33/dV3SrZKYQRhtoCulHYhWckRNo2Z0xBImRxFxDA05b1B0oHoYKCzm
j/H+4WsO+XAFGNp03Ar7+KdQdE7yJ/eXQAW4g9cWca1VOJoRwGUa7TSsV8FclWz7
8RsO/FUjBa3R66j0BUo3/sPkizhzF9fzUB/wsNgDu7T/n4CVpYB9A9eRGMffeabc
bHRUE/6mxWkvAmDFDE1w7MNyZvXZNfHUtAheTX8ldKVSEOaNu6CLM4anp+43Bgpu
fgic5JFl4i/NxW19zC/jCzsnh4ccGtVErrjXnGj7PBA/4oNdwSREzT+RB/geq8Qt
Krsemo1zDROnUHq2wUKWR3fiXd/L6lKispHXeDLzCn1WnSo60hd2hOZRB7Dzhh/D
UxSGC6vdvZF0n49mIav8QvrlFspb0fFbxoiiQ0ZjAghOYGG69gnZWNGwZwPoanUf
wkNhdXcngROuGdznEkZ53F512Qab2jdXC9G/acye1Oq1qoGBLONodnvLJz2Wfvlw
WdSuwsukwz/JrCLj88cymOTOs3ys6hA5QfuzOLyl7w1wnHUS5qSsuxY7LAR/zlss
UjpicGsz75YaalQXGri0kwz0cRqcKE47u3MHHbS2NfH3jmYvpeg=
=LMz2
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.