| 1 |
On Sunday 30 March 2008, Ulrich Mueller wrote: |
| 2 |
> >>>>> On Sun, 30 Mar 2008, Mike Frysinger wrote: |
| 3 |
> >> |
| 4 |
> >> And IMHO the "emacs" USE flag should not be used here: |
| 5 |
> >> |
| 6 |
> >> $ ./configure -hs |
| 7 |
> >> Configuration of Leafpad 0.8.12: |
| 8 |
> >> |
| 9 |
> >> Optional Features: |
| 10 |
> >> [...] |
| 11 |
> >> --enable-emacs implement Emacs key theme (experimental) |
| 12 |
> >> |
| 13 |
> >> $ equery uses =leafpad-0.8.12 |
| 14 |
> >> [...] |
| 15 |
> >> + + emacs : Adds support for GNU Emacs |
| 16 |
> >> |
| 17 |
> >> As its description says, the flag is intended for GNU Emacs support |
| 18 |
> >> which is not the case here. |
| 19 |
> > |
| 20 |
> > i think the USE flag makes sense. perhaps the description should be |
| 21 |
> > changed. |
| 22 |
> |
| 23 |
> Certainly a USE flag makes sense here, but it shouldn't be USE=emacs. |
| 24 |
> |
| 25 |
> The "emacs" global USE flag is used by 82 other packages (all outside |
| 26 |
> the app-emacs category). Its purpose is always that GNU Emacs specific |
| 27 |
> files are installed; either directly, or indirectly by pulling another |
| 28 |
> package via *DEPEND. |
| 29 |
|
| 30 |
why cant it mean both ? USE flags are intended to control features, not |
| 31 |
dependencies. often times that just happens to translate into dependencies. |
| 32 |
realistically though, anyone who wants "emacs" wants all emacs "things". if |
| 33 |
it were to just pull in the emacs dependency, then that could just as easily |
| 34 |
be accomplished by `emerge emacs` and then we can drop the USE flag entirely. |
| 35 |
-mike |
Archives