On Fri, Jul 5, 2013 at 7:18 PM, Rick "Zero_Chaos" Farina
wrote:
> When we then move onto stage 2, it uses just the packages built during
> stage1 (/tmp/stage1root becomes /). This means, if seed stage has
> mpc.so.0.1 but portage has since included mpc.so.2 that the gcc in
> stage2 is linked agai
On Sat, 2013-07-06 at 00:08 -0700, Matt Turner wrote:
> On Fri, Jul 5, 2013 at 7:18 PM, Rick "Zero_Chaos" Farina
> wrote:
> > When we then move onto stage 2, it uses just the packages built during
> > stage1 (/tmp/stage1root becomes /). This means, if seed stage has
> > mpc.so.0.1 but portage has
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/06/2013 03:08 AM, Matt Turner wrote:
> On Fri, Jul 5, 2013 at 7:18 PM, Rick "Zero_Chaos" Farina
> wrote:
>> When we then move onto stage 2, it uses just the packages built during
>> stage1 (/tmp/stage1root becomes /). This means, if seed stage
On Thu, 20 Jun 2013 10:39:54 +0200
Fabio Erculiani wrote:
> The final outcome I would love to see is that everybody eventually
> graduates from kindergarten :-)
> And perhaps introduce a "culture-fit" score in the recruiting,
> mentoring process.
Maybe we should require everyone to be able to re
On Thu, 04 Jul 2013 09:31:35 -0700
Brian Dolbec wrote:
> Thank you for the extra effort. I appreciate it, although for the
> one I had recently, it made it harder. I had just migrated the
> ebuild to the new python eclasses. So the diff included the reversal
> of those changes too.
That happene
On Sat, Jul 6, 2013 at 12:46 AM, Brian Dolbec wrote:
> Yes, it does need to be rebuilt if key deps are updated. The gcc
> produced in the stage1 is broken, so won't run to rebuild itself during
> the stage2 run.
But we keep the old libs around via preserve_libs, and once stage1 is
done we effect
On Sat, Jul 6, 2013 at 8:28 AM, Rick "Zero_Chaos" Farina
wrote:
> You are misremembering that we are using preserve_libs to save our butts
> when mpc is updated and gcc is still linked to the old mpc. I feel very
> uncomfortable as the recommendation of preserve-libs is to remerge as
> soon as po
On Sat, 2013-07-06 at 09:36 -0700, Matt Turner wrote:
> On Sat, Jul 6, 2013 at 12:46 AM, Brian Dolbec wrote:
> > Yes, it does need to be rebuilt if key deps are updated. The gcc
> > produced in the stage1 is broken, so won't run to rebuild itself during
> > the stage2 run.
>
> But we keep the ol
On 07/06/2013 12:39 PM, Matt Turner wrote:
On Sat, Jul 6, 2013 at 8:28 AM, Rick "Zero_Chaos" Farina
wrote:
You are misremembering that we are using preserve_libs to save our butts
when mpc is updated and gcc is still linked to the old mpc. I feel very
uncomfortable as the recommendation of pre
