| 1 |
Check the configure script that comes with the program (assuming there |
| 2 |
is one :) ). Usually, you can do something like (not perfect syntax, |
| 3 |
but you get the idea): |
| 4 |
------------------- |
| 5 |
|
| 6 |
use gtk || ${myconf} = "${myconf} --disable-gtk" |
| 7 |
|
| 8 |
... |
| 9 |
|
| 10 |
|
| 11 |
./configure ${myconf} |
| 12 |
|
| 13 |
|
| 14 |
-------------------- |
| 15 |
or something to that affect (and assuming that the configure option is |
| 16 |
disable-gtk) |
| 17 |
|
| 18 |
On Wed, Nov 20, 2002 at 01:32:40AM +0100, Johannes Ball? wrote: |
| 19 |
> Would it be considered bad practice to put a dependency like "gtk? ( gtk... )" |
| 20 |
> into the ebuild, but leave it to the configure script to sort out whether gtk |
| 21 |
> is installed or not (hence, whether to compile the gtk tools or not)? |
| 22 |
> |
| 23 |
|
| 24 |
-- |
| 25 |
gentoo-dev@g.o mailing list |
Archives