From owner-svn-ports-all@FreeBSD.ORG Fri Sep 12 12:24:48 2014 Return-Path: Delivered-To: svn-ports-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5FC32B09; Fri, 12 Sep 2014 12:24:48 +0000 (UTC) Received: from ainaz.pair.com (ainaz.pair.com [209.68.2.66]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C6F9199D; Fri, 12 Sep 2014 12:24:47 +0000 (UTC) Received: from [192.168.0.132] (vie-188-118-244-060.dsl.sil.at [188.118.244.60]) by ainaz.pair.com (Postfix) with ESMTPSA id 34C463F47F; Fri, 12 Sep 2014 08:24:46 -0400 (EDT) Date: Fri, 12 Sep 2014 14:24:44 +0200 (CEST) From: Gerald Pfeifer To: Tijl Coosemans Subject: Re: svn commit: r351936 - in head: . Mk Mk/Uses archivers/libcomprex archivers/libdynamite archivers/liborange archivers/librtfcomp archivers/lzo2 archivers/ucl archivers/unshield audio/gstreamer1-plug... In-Reply-To: <20140709161049.600ed308@kalimero.tijl.coosemans.org> Message-ID: References: <201404231325.s3NDPHrv045503@svn.freebsd.org> <20140702164609.000d0561@kalimero.tijl.coosemans.org> <20140709161049.600ed308@kalimero.tijl.coosemans.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: svn-ports-head@freebsd.org, svn-ports-all@freebsd.org, Baptiste Daroussin , ports-committers@freebsd.org X-BeenThere: svn-ports-all@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: SVN commit messages for the ports tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Sep 2014 12:24:48 -0000 On Wed, 9 Jul 2014, Tijl Coosemans wrote: >> The primary difference I can see if I add USES=libtool on top is that >> I get a couple of libraries like the following ones: >> >> prefix/gcc410/lib/gcc410/libstdc++.so.6.0.21 >> prefix/gcc410/lib/gcc410/libstdc++.so.6.0.21-gdb.py >> prefix/gcc410/lib/gcc410/libcilkrts.so.5.0.0 >> prefix/gcc410/lib/gcc410/libssp.so.0.0.0 >> prefix/gcc410/lib/gcc410/libquadmath.so.0.0.0 >> prefix/gcc410/lib/gcc410/libgfortran.so.3.0.0 >> prefix/gcc410/lib/gcc410/libobjc.so.4.0.0 >> prefix/gcc410/lib/gcc410/libgcj.so.15.0.0 >> prefix/gcc410/lib/gcc410/libgij.so.15.0.0 >> prefix/gcc410/lib/gcc410/libgcj-tools.so.15.0.0 >> prefix/gcc410/lib/gcc410/libgomp.so.1.0.0 >> prefix/gcc410/lib/gcc410/libitm.so.1.0.0 >> prefix/gcc410/lib/gcc410/libatomic.so.1.1.0 >> prefix/gcc410/libexec/gcc410/gcc/i386-portbld-freebsd10.0/4.10.0/liblto_plugin.so.0.0.0 >> >> So, should I still add USES=libtool to these ports? > Yes. This new version scheme reduces future library version bumps. I think I get that in general, but how so in case of the lang/gcc* ports? Due to libgcc_s.so, among others, I do not see how PORTREVISION bumps are reduced when upgrading lang/gcc (which is the only case where we have had to do this). (This is why I had not gone ahead making this change, but see that you know committed this yesterday.) Gerald