| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Raúl Porcel wrote: |
| 5 |
> Vlastimil Babka wrote: |
| 6 |
>> Raúl Porcel wrote: |
| 7 |
>>> Agreed from mozilla. |
| 8 |
>>> firefox and seamonkey already have the global use-flag |
| 9 |
>> Is there any guideline from mozilla team about what to do when there are |
| 10 |
>> more than one of these flags (firefox/seamonkey/xulrunner) supported by |
| 11 |
>> package AND enabled by user? Some of those local flag descriptions |
| 12 |
>> suggest that USE="firefox xulrunner" results in using xulrunner (so it |
| 13 |
>> has higher priority). So is that recommended, and how about seamonkey? |
| 14 |
> |
| 15 |
> |
| 16 |
> Sorry, didn't saw this msg. |
| 17 |
> |
| 18 |
> I don't know of any guideline. Anyway all apps should start to use |
| 19 |
|
| 20 |
Well maybe I could've just read the USE flags descriptions closely and |
| 21 |
it would be clear to me that the preference order should probably be: |
| 22 |
|
| 23 |
xulrunner > firefox > seamonkey |
| 24 |
|
| 25 |
> xulrunner, since that's what they really want instead of using firefox |
| 26 |
> or seamonkey. When ff-3.0 is released no app will be able to build |
| 27 |
> against ff, since ff will build against xulrunner. So, what i said, apps |
| 28 |
> should use xulrunner as primary option, now that xulrunner is up-to-date |
| 29 |
> and working fine. |
| 30 |
|
| 31 |
We should probably fix |
| 32 |
profiles/default-linux/x86/2007.0/desktop/make.defaults then (and |
| 33 |
possibly other profiles?), as it has only firefox in USE? |
| 34 |
- -- |
| 35 |
Vlastimil Babka (Caster) |
| 36 |
Gentoo/Java |
| 37 |
-----BEGIN PGP SIGNATURE----- |
| 38 |
Version: GnuPG v1.4.7 (GNU/Linux) |
| 39 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org |
| 40 |
|
| 41 |
iD8DBQFGaVXwtbrAj05h3oQRAifRAKCmsFjAuyHUdBUgxCsAjjxd5ojfuACfcYF4 |
| 42 |
rx+vUQNY81RxzrfZCEvmxxQ= |
| 43 |
=sqC9 |
| 44 |
-----END PGP SIGNATURE----- |
| 45 |
-- |
| 46 |
gentoo-dev@g.o mailing list |
Archives