[arch-dev-public] Doing a rebuild of [core]?
a.radke at arcor.de
Thu Nov 18 06:52:21 CET 2010
Am Thu, 18 Nov 2010 14:16:34 +1000
schrieb "Allan McRae" <allan at archlinux.org>:
> I was thinking of doing a fairly large rebuild of packages in [core]
> for the following reasons:
> - The toolchain is quite good at the moment and many packages have
> not been built in a long time so could use a refresher build to take
> advantage of what the newer toolchain offers (~15 packages are > 1
> year old). I expect a toolchain update to happen in the next few
> weeks so this is a good time.
What update do you expect? Usually a rebuild is useful to catch
up latest major gcc improvements. Gcc4.6 is still in an early
stage. Maybe we should delay it until the gcc4.6 release.
The toolchain improvements over the last 2 years were of minor
advantages. So I don't expect major performance improvements.
Getting the packages into xz compression format and pkg pool would be
One concern for a rebuild right now: most packagers allowed for
pushing packages into core haven't been much online lately. Not sure
if they can spend that much time. Sadly "makeworld" has died. But I
remember Daniel made such a rebuild script locally (was at gcc4.3
More information about the arch-dev-public