On Wed, Dec 23, 2009 at 2:20 PM, Daniel Ouellet <daniel@presscom.net> wrote:
quoted text
> Just for the records, this libc was bump up at the H2K9, witch is totally
> fine for sure and I have no issue or complains about it.
>
> Log entry is clear about it
>
> "Bump the libc major for the post-h2k9 string of ABI changes and additions
> (rthreads, MB_LEN_MAX, rdomains)"

Yep, lib version bumps are postponed before and during hackathons so
that the developers at the hackathon can have a (relatively) full set
of up-to-date and consistent packages available for whatever they're
doing.  Indeed, the changes that triggered the bump weren't actually
from the hackathon itself.


quoted text
> I am only wonder if when this happened if the various packages that depend
> on them for example are redone. I know there was cut back in the pass as
> well for lack of men power for this.

"It depends."  The package build machines have to be updated to the
new base and it takes weeks for a full package build run to complete
(6 weeks for some of the slower archs, IIRC).  It looks like the
sparc64 package builds were in the middle of a run when the bump
occurred, so it may have been felt better to let it complete to help
detect any problems with recent ports changes instead of interrupting
it and starting afresh.

...but I'm not a ports or package build person, so I'm not really up
on the details.  Perhaps this question should be directed to the
ports@ mailing list?


Philip Guenther