[gentoo-catalyst] catalyst wants to build kazehakase against firefox even with xulrunner flag set

[gentoo-catalyst] catalyst wants to build kazehakase against firefox even with xulrunner flag set

[ducasse.isidore]

I succeeded in building kazehakase against xulrunner libs on my x86_64 station. But catalyst on the same system pulls in firefox systematically when the livecd-stage1.spec file mentions kazehakase, even if it contains the xulrunner USE flag.

This is amazing since almost nothing change between both: mainly, catalyst refused to use amd64 so I had to switch to subarch=athlon-xp ; and my livecd uses the 2007.1 profile. Can any of those two differences be of incidence to my problem? _why_?

Thanks in advance.
-- 
gentoo-catalyst@gentoo.org mailing list

Re: [gentoo-catalyst] catalyst wants to build kazehakase against firefox even with xulrunner flag set

[Chris Gianelloni]

[-- Attachment #1: Type: text/plain, Size: 1140 bytes --]

On Sun, 2007-02-25 at 16:51 +0100, ducasse.isidore@gmail.com wrote:
> I succeeded in building kazehakase against xulrunner libs on my x86_64 station. But catalyst on the same system pulls in firefox systematically when the livecd-stage1.spec file mentions kazehakase, even if it contains the xulrunner USE flag.
> 
> This is amazing since almost nothing change between both: mainly, catalyst refused to use amd64 so I had to switch to subarch=athlon-xp ; and my livecd uses the 2007.1 profile. Can any of those two differences be of incidence to my problem? _why_?

It's either a problem in your configuration or a bug in the package.
All catalyst does is call portage, anyway.

As for using the 2007.0 profile... Don't... ever.  Never use a profile
that isn't released, as they're likely to be screwed up at any point in
time, since we're testing them and expect anyone using them to be
developers, capable of fixing bugs themselves (including commits... ;] )

-- 
Chris Gianelloni
Release Engineering Strategic Lead
Alpha/AMD64/x86 Architecture Teams
Games Developer/Council Member/Foundation Trustee
Gentoo Foundation

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-catalyst] catalyst wants to build kazehakase against firefox even with xulrunner flag set

[ducasse.isidore]

On Sun, 25 Feb 2007 21:21:54 -0500
Chris Gianelloni <wolf31o2@gentoo.org> wrote:

> As for using the 2007.0 profile... Don't... ever.  Never use a profile
> that isn't released, as they're likely to be screwed up at any point in
> time, since we're testing them and expect anyone using them to be
> developers, capable of fixing bugs themselves (including commits... ;] )

What does "commits" mean? Is it about how to report a [real] bug? I'm not a developer anyway.

Thanks for the quick answering. I'll stick on your good remarks.

BTW may I post a success story about catalyst on the list? (soon to come)
-- 
gentoo-catalyst@gentoo.org mailing list

Re: [gentoo-catalyst] catalyst wants to build kazehakase against firefox even with xulrunner flag set

[Andrew Gaffney]

ducasse.isidore@gmail.com wrote:
> On Sun, 25 Feb 2007 21:21:54 -0500
> Chris Gianelloni <wolf31o2@gentoo.org> wrote:
> 
>> As for using the 2007.0 profile... Don't... ever.  Never use a profile
>> that isn't released, as they're likely to be screwed up at any point in
>> time, since we're testing them and expect anyone using them to be
>> developers, capable of fixing bugs themselves (including commits... ;] )
> 
> What does "commits" mean? Is it about how to report a [real] bug? I'm not a developer anyway.

It means being able to commit to CVS to *actually* fix the bug instead of just 
figuring out how to fix it locally.

-- 
Andrew Gaffney                            http://dev.gentoo.org/~agaffney/
Gentoo Linux Developer                                   Installer Project
-- 
gentoo-catalyst@gentoo.org mailing list

Re: [gentoo-catalyst] catalyst wants to build kazehakase against firefox even with xulrunner flag set

[Chris Gianelloni]

[-- Attachment #1: Type: text/plain, Size: 1910 bytes --]

On Mon, 2007-02-26 at 16:49 +0100, ducasse.isidore@gmail.com wrote:
> On Sun, 25 Feb 2007 21:21:54 -0500
> Chris Gianelloni <wolf31o2@gentoo.org> wrote:
> 
> > As for using the 2007.0 profile... Don't... ever.  Never use a profile
> > that isn't released, as they're likely to be screwed up at any point in
> > time, since we're testing them and expect anyone using them to be
> > developers, capable of fixing bugs themselves (including commits... ;] )
> 
> What does "commits" mean? Is it about how to report a [real] bug? I'm not a developer anyway.

No, it means unless you can fix it yourself, don't use it.  This means
you really need to be a developer.  I break the profiles *ON PURPOSE*
quite a lot prior to release to test things.  Quite honestly, I don't
care if anyone is using the profiles, since they're under dev and I've
added about as much warning as I can via the README explaining that if
it doesn't work as expected, it's not a bug, but a feature.  ;]

Basically, don't ever use any profiles you see in the tree higher than
the latest release version stages on the mirrors.  The only reason you
*ever* would do so is if the architecture team of Release Engineering
has asked for testing and you're assisting.  Anything else is asking for
trouble.

Another thing is that we're known to leave dev profiles in the tree
after we've done our release snapshot.  We test and make changes in the
snapshot, then commit all the fixes to the tree at once when we move the
profile out of dev.  Again, save yourself some headache and simply don't
use them.

> Thanks for the quick answering. I'll stick on your good remarks.
> 
> BTW may I post a success story about catalyst on the list? (soon to come)

-- 
Chris Gianelloni
Release Engineering Strategic Lead
Alpha/AMD64/x86 Architecture Teams
Games Developer/Council Member/Foundation Trustee
Gentoo Foundation

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]