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...

[Gerald Pfeifer]

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