1 |
Duncan Coutts wrote: |
2 |
> On Thu, 2006-09-21 at 20:27 +0200, Luca Barbato wrote: |
3 |
>> Duncan Coutts wrote: |
4 |
>> |
5 |
>>> So my point is, I don't think it can be simply dismissed as ABI nonsense |
6 |
>>> that we don't have to deal with. Being able to SLOT on the compiler |
7 |
>>> flavour (and possibly version) would allow us to do useful things that |
8 |
>>> we cannot currently do. |
9 |
>> what about making them build what you want depending on useflags? |
10 |
> |
11 |
> Aye, for the implementation flavours that's probably the way to go once |
12 |
> we have use-deps. We'll have to hold off on multiple versions of the |
13 |
> same compiler though. |
14 |
> |
15 |
> It might get a bit hairy though :-) |
16 |
> |
17 |
> DEPEND="ghc? ( dev-haskell/foo @ ghc ) |
18 |
> hugs? ( dev-haskell/foo @ hugs ) |
19 |
> yhc? ( dev-haskell/foo @ yhc ) |
20 |
> jhc? ( dev-haskell/foo @ jhc )" |
21 |
> |
22 |
> (I've not looked up what the use-dep syntax is, I'm just guessing) |
23 |
|
24 |
as now, you can handle that with an eclass that takes deps, checks those |
25 |
deps with certain use if the use has been enabled and dies if those |
26 |
criterions aren't meet (asking you to falling back to hc-updater to keep |
27 |
those applications in shape) |
28 |
|
29 |
pretty hacky and itchy but that's probably the best you can do w/out |
30 |
use-deps. (PS can you slot on use now?) |
31 |
|
32 |
lu |
33 |
|
34 |
-- |
35 |
|
36 |
Luca Barbato |
37 |
|
38 |
Gentoo/linux Gentoo/PPC |
39 |
http://dev.gentoo.org/~lu_zero |
40 |
|
41 |
-- |
42 |
gentoo-dev@g.o mailing list |