Quoting Pawel Jakub Dawidek <[EMAIL PROTECTED]> (from Mon, 27 Aug 2007 15:56:25 +0200):

On Mon, Aug 27, 2007 at 08:50:19AM -0400, John Baldwin wrote:

Folks running -current are also committers that use -current to test as
much as they can, but also to use it for day-to-day work. Isn't it why
we have perforce and other policies, so that -current can be stable and
usable? If we have tools that can help -current users to use the system
smoothly, I'm all for using them. I can't imagine taking yet another two
days and reinstalling all ports, just because -current users are not

Only 2 days? Lucky you, I'm just through a complete recompile of every port after the gcc 4.2.1 import (unluckily 4.2.1 doesn't fix all known bugs) just to be on the safe side, and a complete recompile after the gcc 4.2.0 import... and it takes nearly a week on my machine.

important. Of course -current users know how to deal with things like
this, but that doesn't mean they have to if there is another way.
The more surprises like that one, the less -current users we will have,
which means the less testing.
If there will be a need for me to reinstall all the ports I'll choose
not to upgrade or downgrade to 6.x...

So the really important thing for you is: How many ports are affected by this change?

Does anyone have an estimate for this?

If not, does someone has an exhaustive list of affected symbols? I can write a short script which has a look into each installed port to determine if it is affected or not (based upon the assumption that you don't mind if we overlook a few things... I'm not sure if statically linked binaries contain enough information).

Bye,
Alexander.

--
The very remembrance of my former misfortune proves a new one to me.
                -- Miguel de Cervantes

http://www.Leidinger.net    Alexander @ Leidinger.net: PGP ID = B0063FE7
http://www.FreeBSD.org       netchild @ FreeBSD.org  : PGP ID = 72077137
_______________________________________________
cvs-all@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/cvs-all
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Reply via email to