Date: Wed, 13 Apr 2022 01:44:47 +0100 From: tech-lists <tech-lists@zyxst.net> To: freebsd-questions@freebsd.org Subject: Re: Changes (was: nvidia-driver and no update in /usr/ports/UPDATING) Message-ID: <YlYc/91DTwp5aoMP@cloud9.zyxst.net> In-Reply-To: <16715f81-49c7-9710-d4f4-2a555f0eff74@gmail.com> References: <Yk9tEmvtQB5JEWoz@cloud9.zyxst.net> <Yk%2Bfip5KdWYjn99h@cloud9.zyxst.net> <16715f81-49c7-9710-d4f4-2a555f0eff74@gmail.com>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On Mon, Apr 11, 2022 at 05:44:28PM +0100, Graham Perrin wrote: > Did you also rant about the commit message for ><https://github.com/adobe-fonts/source-sans/commiti >/411dc97c6b9b60301edaf6cc0fa04053b0f56dd4>? No I did not. But I'm I'm sorry I ranted here, truly. It was an emotional outburst. But trust is an emotional thing. I can't trust ports right now to do the right thing. I have many freebsd vms to decomission and replace now with something else, because of this fact. There are some I must not be blindsided like this on. I accept stuff changes, having used freebsd and the ports collection since 1997. I can and have done when needs be work with and round issues with PRs, and I am very grateful for both in ports and src to have this great ecosystem provided by volounteers. But if you've read this thread, you will understand it wasn't about any one port. It was about not updating UPDATING when a port changes name (in this example). It's not a bug. To avoid the issue requires hardly any work from the committer, if it is indeed the committer who would update this file (I don't actually know, it might be another department or group). Just a note at the top of the file in /usr/ports/UPDATING. Ideally before an update is committed. I see there is still no note in UPDATING for nvidia-driver in ports-579962. This means that anyone with PORTS_MODULES+=x11/nvidia-driver in their /etc/src.conf who updates their stable/13 world/kernel and who has eg a GeForce (640 for example) will not be able to load xorg when their system reboots. Because the wrong kernel driver was compiled. Because the name change wasn't in UPDATING. -- J. [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEE8n3tWhxW11Ccvv9/s8o7QhFzNAUFAmJWHPYACgkQs8o7QhFz NAXY+Q//W5wcfXAyOuRxQWn1BYWm7Vt9S0UdMclxu4guHZs5YPkp2O6MaCV91+2W 1fnVtwgiXITwsSxMFgMbf4+a3T70+PRzh+jVUrwzwB4fJj2IzVz9W4dREnOBsQ19 9HsWAKb3k/EGmSsjWOxJC8k81ipIqHU4qLhN2JO5uv0UZAVGCSKVHbL7XXFSozUp guLZA57jMS4yCFU4GsyEUJc+RTP/42xKxZNaJ9R1Il9EGRXaVF8qje5xvoB9jCma J8GzNotaZRK6MYuQn3DaXfnAW2O2PCOeBkhoxcCz0O/kTAl0UssEzW0S7S3ESpM0 KN/nlvxEUhUrWFZDhZx83GPaXaKcPOBeowR01Ax6giQcITd0Y0qN7honDR9qbxmA fWyAgo80InqsQKH2IB0RQXzwJShiUe/HzHfgauLrRucnjw7q4sX+EaglE8q16tEH AWDjH+iLlm3FcL2YrX4/REh+EGMghppnufw2WLJxJoDlefzvnMl7Z2QMmNoaLJoe obELzdCN2YHgTbkM4Ga2DK+4tZjLdnh6AS9a74eU24X8UC6VDu9H2KoNXGyrVwJc k87QpPaMEIaX0OUV830vqwqQnZ0A7dFUmkzEvyhJsSrZn3NWAmhwaKqF0Dd7aVky A1Cjbe16iyc0NCZMMX/v5KnruZJ7zzSy9B4oJnSyoYo0y4KEojY= =vpk5 -----END PGP SIGNATURE-----home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?YlYc/91DTwp5aoMP>