Re: [gentoo-catalyst] libtool dependencies in stage3
Same problem here.. Mike, does the patch works for you? Luca Il giorno 28/ago/07, alle ore 16:32, Mike Frysinger ha scritto: On Tuesday 28 August 2007, Åsmund Grammeltvedt wrote: Still, is it impossible for features to carry over from packages in the bootstrap stage and affecting depending packages before the dependency is reemerged, without this being a bug in the depending package? speaking generally, probably ... but here, it is a bug in attr, pure and simple ... it should not be using the host libtool someone posted a bug + fix for this, ive just been sitting on it -mike -- [EMAIL PROTECTED] mailing list
Re: [gentoo-catalyst] libtool dependencies in stage3
On Tuesday 28 August 2007 16:32:39 Mike Frysinger wrote: On Tuesday 28 August 2007, Åsmund Grammeltvedt wrote: Still, is it impossible for features to carry over from packages in the bootstrap stage and affecting depending packages before the dependency is reemerged, without this being a bug in the depending package? speaking generally, probably ... but here, it is a bug in attr, pure and simple ... it should not be using the host libtool Ok, I'm mostly trying to justify messing with /var/db/pkg to myself. Cleaning it out and bootstrapping from there seems like it would reduce the impact of such bugs. -- Åsmund Grammeltvedt Snap TV signature.asc Description: This is a digitally signed message part.
Re: [gentoo-catalyst] libtool dependencies in stage3
On Tuesday 28 August 2007, Åsmund Grammeltvedt wrote: On Tuesday 28 August 2007 16:32:39 Mike Frysinger wrote: On Tuesday 28 August 2007, Åsmund Grammeltvedt wrote: Still, is it impossible for features to carry over from packages in the bootstrap stage and affecting depending packages before the dependency is reemerged, without this being a bug in the depending package? speaking generally, probably ... but here, it is a bug in attr, pure and simple ... it should not be using the host libtool Ok, I'm mostly trying to justify messing with /var/db/pkg to myself. Cleaning it out and bootstrapping from there seems like it would reduce the impact of such bugs. then you'd hit things like portage going crazy over package collisions ... or in the scenario where the older stage had an older version and the newer version has different files so you're left with orphaned cruft ... -mike signature.asc Description: This is a digitally signed message part.
Re: [gentoo-catalyst] libtool dependencies in stage3
On Tue, 2007-08-28 at 10:51 -0400, Mike Frysinger wrote: On Tuesday 28 August 2007, Åsmund Grammeltvedt wrote: On Tuesday 28 August 2007 16:32:39 Mike Frysinger wrote: On Tuesday 28 August 2007, Åsmund Grammeltvedt wrote: Still, is it impossible for features to carry over from packages in the bootstrap stage and affecting depending packages before the dependency is reemerged, without this being a bug in the depending package? speaking generally, probably ... but here, it is a bug in attr, pure and simple ... it should not be using the host libtool Ok, I'm mostly trying to justify messing with /var/db/pkg to myself. Cleaning it out and bootstrapping from there seems like it would reduce the impact of such bugs. then you'd hit things like portage going crazy over package collisions ... or in the scenario where the older stage had an older version and the newer version has different files so you're left with orphaned cruft ... Correct. There is a reason that we moved *away* from removing the /var/db/pkg stuff for stage1. This is it. -- Chris Gianelloni Release Engineering Strategic Lead Alpha/AMD64/x86 Architecture Teams Games Developer/Council Member/Foundation Trustee Gentoo Foundation signature.asc Description: This is a digitally signed message part
Re: [gentoo-catalyst] libtool dependencies in stage3
On Tuesday 28 August 2007 19:56, Chris Gianelloni wrote: On Tue, 2007-08-28 at 10:51 -0400, Mike Frysinger wrote: On Tuesday 28 August 2007, Åsmund Grammeltvedt wrote: On Tuesday 28 August 2007 16:32:39 Mike Frysinger wrote: On Tuesday 28 August 2007, Åsmund Grammeltvedt wrote: Still, is it impossible for features to carry over from packages in the bootstrap stage and affecting depending packages before the dependency is reemerged, without this being a bug in the depending package? speaking generally, probably ... but here, it is a bug in attr, pure and simple ... it should not be using the host libtool Ok, I'm mostly trying to justify messing with /var/db/pkg to myself. Cleaning it out and bootstrapping from there seems like it would reduce the impact of such bugs. then you'd hit things like portage going crazy over package collisions ... or in the scenario where the older stage had an older version and the newer version has different files so you're left with orphaned cruft ... Correct. There is a reason that we moved *away* from removing the /var/db/pkg stuff for stage1. This is it. I see. Thanks for the clarifications! -- Åsmund Grammeltvedt Snap TV -- [EMAIL PROTECTED] mailing list
