From owner-freebsd-ports@FreeBSD.ORG  Wed Dec 12 08:34:11 2012
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
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 22D274D5
 for <ports@freebsd.org>; Wed, 12 Dec 2012 08:34:11 +0000 (UTC)
 (envelope-from lists@opsec.eu)
Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1])
 by mx1.freebsd.org (Postfix) with ESMTP id CB64F8FC15
 for <ports@freebsd.org>; Wed, 12 Dec 2012 08:34:10 +0000 (UTC)
Received: from pi by home.opsec.eu with local (Exim 4.77 (FreeBSD))
 (envelope-from <lists@opsec.eu>)
 id 1Tihla-0009q8-LI; Wed, 12 Dec 2012 09:34:10 +0100
Date: Wed, 12 Dec 2012 09:34:10 +0100
From: Kurt Jaeger <lists@opsec.eu>
To: Matthieu Volat <mazhe@alkumuna.eu>
Subject: Re: [RFC/HEADSUP] portmaster default -w (preserve shared libraries)
Message-ID: <20121212083410.GZ12114@home.opsec.eu>
References: <50C7576C.5040100@FreeBSD.org>
 <20121212075144.ca3881329b4aa461c38c942e@alkumuna.eu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20121212075144.ca3881329b4aa461c38c942e@alkumuna.eu>
Cc: FreeBSD Ports <ports@freebsd.org>
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Dec 2012 08:34:11 -0000

Hi!

> > (As maintainer) I'm proposing to make -w the default for portmaster.
> > This will preserve old shared libraries when upgrading. This helps 2 things:
> > 
> > [...]
> 
> I have a few question about what happens if you always use this flag: 
> * Do you keep every version of the shlibs you ever built on your system?

No, only those that still needed.

> * Are there any method to clean the unused ones?

sysutils/libchk or pkg_libchk from sysutils/bsdadminscripts.

> * What do we do about libraries versions that have security issues
> and that we need to get out asap?

Currently: The admin decides how he wants to handle this.

If there is a efficient way to handle this, most admins will use it.

I do not see an time- and cpu-efficient way, right now 8-(

-- 
pi@opsec.eu            +49 171 3101372                         8 years to go !