Date: Tue, 11 Dec 2012 09:55:24 -0600 From: Bryan Drewery <bdrewery@freebsd.org> To: FreeBSD Ports <ports@freebsd.org> Subject: [RFC/HEADSUP] portmaster default -w (preserve shared libraries) Message-ID: <50C7576C.5040100@FreeBSD.org>
next in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig811FD9DE60957647A683B1C6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable (As maintainer) I'm proposing to make -w the default for portmaster. This will preserve old shared libraries when upgrading. This helps 2 thin= gs: 1. Prevents a broken system during upgrades 2. Prevents a broken system after upgrading for ports that did not get a PORTREVISION bump from a shared library update. You have certainly ran into this problem with large library updates such as png, pcre, openssl, etc. Portupgrade has always done this as default, and I have never seen any problems arise from it. It also cleans up prevents duplicated library versions. If portmaster is not already doing this, I will ensure it does.= You could then use pkg_libchk to rebuild any lingering ports if you wanted to ensure your system was using the latest. Then cleanout the preserved shared library. Of course there will be a way to stick to the old default of not preserving the libraries. Someone may consider this a POLA violation, but I consider that a broken system from missing libraries and PORTREVISION bumps is more of a POLA violation. The other option to ensuring that all ports work correctly after a shared library update is to just rebuild any port which recursively is affected by another port being updated. I think this is fine in scenarios such as tinderbox/poudriere, but with end-user compiling ports on their system, this may quickly become too much of a burden. Regards, Bryan Drewery --------------enig811FD9DE60957647A683B1C6 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iQIcBAEBAgAGBQJQx1dxAAoJEG54KsA8mwz5L+UQAIHBLr/7anTy9HQkPe8CbOUW QWlZOlTu/gILhk9q7wFwD319dswEdDBpbe5UIcdVaAqDn3C43y4+91z++IozmeC+ Ww9/aG/Q+O4/6lRvc3cI8BXXs2WKP+6J54MbMVpM8vUJnN6YEerFcI4bJh41uWZG qglHhfRy07c0dvrl+hjCyeMrWVWrIsaTv6XoJhGQDPI7k2lDDx/6LotWcIBaeBVS M4ZmDYQrdY1G2+sR3r2ESxVoo35K/3qQSOlyDHUbwA1pI8HOPMud4jTcwburBpCl lRV8UnI7Wd1nmwU8SM3O3oz4nC2GDdLX8qttzOQEj+Svk7R1QT7Qd1uNuRenZept YkeavTn0USLVzXHgkge03kqbUnmB1uVqEsoITQNyC6BaEUgFI1DrohXAmSAEtsv9 5SqkIaoBHw7/GEM9TlEdX/muqQNtzEMI6YmjJCQ5oPj/mhFUUQ6irXTv0bKTrubl Nsul4b2ERpxFNZbAsovcp8lx62/0QXAsVMmSzOu4/wWOXKFbxzZEz1PBCVqcy719 XNzYZOqi5JnFD+bAk2ojGnegn5klKLkBjuscekJ3y/iYZ7Qyyg2R0PpX95kvb9BQ 43LeOi/Nz5I1wiTR1wlJuhHTf0qCX/Q0cxl6ji9IseZLQf3R8vUzc2L/ygKtJS27 a6/2HVINtXM/3JetcmGL =xjdB -----END PGP SIGNATURE----- --------------enig811FD9DE60957647A683B1C6--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?50C7576C.5040100>