From owner-freebsd-ports@FreeBSD.ORG Tue Dec 11 16:16:01 2012 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2B944552; Tue, 11 Dec 2012 16:16:01 +0000 (UTC) (envelope-from kpaasial@gmail.com) Received: from mail-vc0-f182.google.com (mail-vc0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id BDB538FC0C; Tue, 11 Dec 2012 16:16:00 +0000 (UTC) Received: by mail-vc0-f182.google.com with SMTP id fo14so4975358vcb.13 for ; Tue, 11 Dec 2012 08:16:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=LDAa/vNtxRLTeyDxoeB8WhG0zHyt4375UtVgZx0qkkQ=; b=0whWf8FlKfrJ+RnxhyjczVu3Whwy3GfCS/1TpW+v2Cqk15vxMJijiCQ+RUzwirQ4Oh 0zV/G6F4CxL85eJJPkrzSMzs1CbBwXzgV7T3BHVJwHn4rbl/UwhP16gzcwRI+Bdpp6+i sxCvGorlZ5NzQF2syK+A79byqV/shHK3bEF/p4vMwMeBhaQf1YxVN5vNw6tWYuTqgaHv cwf2lgnP66AzvZNRVZAdRpt5QpZfkzVdcietKnaf1ovgJnVaw/riHfSiwixSx9I4zzb7 0O3pqkLE45bm3WkdmM4vi0Xub4xYPg9bSq0rq3zkXKr1xKv7j9xyid6/OJhm3jxUHZ8b gCAA== MIME-Version: 1.0 Received: by 10.59.11.67 with SMTP id eg3mr8675679ved.31.1355242560087; Tue, 11 Dec 2012 08:16:00 -0800 (PST) Received: by 10.58.209.163 with HTTP; Tue, 11 Dec 2012 08:16:00 -0800 (PST) In-Reply-To: <50C7576C.5040100@FreeBSD.org> References: <50C7576C.5040100@FreeBSD.org> Date: Tue, 11 Dec 2012 18:16:00 +0200 Message-ID: Subject: Re: [RFC/HEADSUP] portmaster default -w (preserve shared libraries) From: Kimmo Paasiala To: Bryan Drewery Content-Type: text/plain; charset=UTF-8 Cc: FreeBSD Ports 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 16:16:01 -0000 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. -Kimmo