From owner-freebsd-ports@FreeBSD.ORG Tue Dec 11 17:42:20 2012 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D4412648 for ; Tue, 11 Dec 2012 17:42:20 +0000 (UTC) (envelope-from Mathias.Picker@virtual-earth.de) Received: from www94.your-server.de (www94.your-server.de [213.133.104.94]) by mx1.freebsd.org (Postfix) with ESMTP id 8AB778FC13 for ; Tue, 11 Dec 2012 17:42:20 +0000 (UTC) Received: from [92.230.244.199] (helo=[192.168.178.33]) by www94.your-server.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.74) (envelope-from ) id 1TiTqU-0001s6-RA for freebsd-ports@freebsd.org; Tue, 11 Dec 2012 18:42:18 +0100 Subject: Re: [RFC/HEADSUP] portmaster default -w (preserve shared libraries) From: Mathias Picker To: freebsd-ports@freebsd.org In-Reply-To: References: <50C7576C.5040100@FreeBSD.org> Content-Type: text/plain; charset="UTF-8" Organization: virtual earth GmbH Date: Tue, 11 Dec 2012 18:42:14 +0100 Message-ID: <1355247734.48552.26.camel@mp> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-Authenticated-Sender: Mathias.Picker@virtual-earth.de X-Virus-Scanned: Clear (ClamAV 0.97.5/15722/Tue Dec 11 18:11:13 2012) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Dec 2012 17:42:20 -0000 Am Dienstag, den 11.12.2012, 18:16 +0200 schrieb Kimmo Paasiala: > On Tue, Dec 11, 2012 at 5:55 PM, Bryan Drewery wrote: > > (As maintainer) I'm proposing to make -w the default for portmaster. > > This will preserve old shared libraries when upgrading. This helps 2 things: > > > > 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 > > > > > > Absolutely yes from me. The -w option is real lifesaver and should be > on by default. +1 Cheers, Mathias > > -Kimmo > _______________________________________________ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org"