| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
On 04/05/12 11:37, "Paweł Hajdan, Jr." wrote: |
| 5 |
> On 5/4/12 8:21 PM, Mike Gilbert wrote: |
| 6 |
>> My 2 cents: The Chromium project really doesn't have any motivation to |
| 7 |
>> make it optional since their end product is Google Chrome and they |
| 8 |
>> target a given version of Ubuntu. I think a patch to make them |
| 9 |
>> optional might be accepted, but it probably isn't going to happen |
| 10 |
>> otherwise. |
| 11 |
> |
| 12 |
> Another point is that too many USE flags for such a big and complex |
| 13 |
> package as www-client/chromium would make testing much much harder, and |
| 14 |
> create many configurations upstream would not support. |
| 15 |
|
| 16 |
I'll check with upstream if that would be a huge problem for them, we |
| 17 |
have 6 useflags and we'd bump them to 8. Firefox has twice of them. |
| 18 |
|
| 19 |
If nobody else wants to I could have a look and see how hard is to make |
| 20 |
that nicer for our non-udev/non-dbus users on linux. |
| 21 |
|
| 22 |
lu |
| 23 |
|
| 24 |
- -- |
| 25 |
|
| 26 |
Luca Barbato |
| 27 |
Gentoo/linux |
| 28 |
http://dev.gentoo.org/~lu_zero |
| 29 |
|
| 30 |
-----BEGIN PGP SIGNATURE----- |
| 31 |
Version: GnuPG v2.0.18 (GNU/Linux) |
| 32 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ |
| 33 |
|
| 34 |
iEYEARECAAYFAk+kMHwACgkQ6Ex4woTpDjTTAgCfXtMJFJjB5ZH08u0Nb7yKmkqv |
| 35 |
/GwAoNejWgUcHaMWnD6e8Bgr/+V/cYDA |
| 36 |
=CCQe |
| 37 |
-----END PGP SIGNATURE----- |
Archives