| 1 |
At 2005-04-22T08:38:22+0900, Georgi Georgiev <chutz@×××.net> wrote: |
| 2 |
> maillog: 21/04/2005-23:43:57(+0200): Diego 'Flameeyes' Petten? types |
| 3 |
> > Same for ieee1394, usually enables support for |
| 4 |
> > media-plugins/libdc1394, sys-libs/libavc1394 and/or |
| 5 |
> > sys-libs/libraw1394. |
| 6 |
> |
| 7 |
> Considering that a person rarely needs *both* libdc1394 and |
| 8 |
> libavc1394, it would be even cooler to have *two* useflags. |
| 9 |
|
| 10 |
Generally, I've noticed that use flags are named for the functionality |
| 11 |
they enable, rather than the libraries that they pull in as depends. It |
| 12 |
might be a cleaner approach to use "ieee1394" or even just "1394" as the |
| 13 |
global flag, and then if any future packages offer a choice between |
| 14 |
libs, add some local flags as appropriate. |
| 15 |
|
| 16 |
-- |
| 17 |
Batou: Hey, Major... You ever hear of "human rights"? |
| 18 |
Kusanagi: I understand the concept, but I've never seen it in action. |
| 19 |
--Ghost in the Shell |
Archives