| 1 |
On Wed, Sep 9, 2015 at 8:10 AM, Alexandre Rostovtsev <tetromino@g.o> |
| 2 |
wrote: |
| 3 |
|
| 4 |
> On Wed, 2015-09-09 at 11:00 -0400, Mike Gilbert wrote: |
| 5 |
> > I would really like a way to toggle gtk3 for testing. If you don't |
| 6 |
> > want to expose it as a 'supported' option for users, then masking it |
| 7 |
> > sounds fine to me. |
| 8 |
> |
| 9 |
> Then add the flag, document it in metadata.xml. |
| 10 |
> |
| 11 |
> But in general, try to avoid using this flag in your ebuilds if |
| 12 |
> possible, the gnome team *really* doesn't want to turn gtk3 into a |
| 13 |
> global USE flag with uncertain semantics. |
| 14 |
|
| 15 |
|
| 16 |
The best way to avoid this IMHO is to not name the flag the same thing. |
| 17 |
|
| 18 |
if you named the chromium flag "experimental-gtk3-ui' or similar, then |
| 19 |
users would be unable to turn it on by just setting 'gtk3' |
| 20 |
|
| 21 |
-A |
Archives