1 |
On Wed, 2003-05-21 at 12:10, Tom Payne wrote: |
2 |
> Hi -- |
3 |
> |
4 |
> I'd like to abuse PROVIDE. Here's the story: |
5 |
> |
6 |
> ruby-1.6.8 is the latest version of Ruby |
7 |
> rexml, yaml, optparse, and others are available as add-on packages |
8 |
> |
9 |
> ruby-1.8.0 is coming Real Soon Now |
10 |
> rexml, yaml, optparse, and others are part of the ruby-1.8.0 distribution |
11 |
> |
12 |
> If a package needs ruby and optparse I can write |
13 |
> DEPEND="( >=dev-lang/ruby-1.6 <dev-lang/ruby-1.8 dev-ruby/optparse ) |
14 |
> || >=dev-lang/ruby-1.8.0" |
15 |
> but this means that I have to modify every ebuild that depends on any of |
16 |
> packages that are now part of ruby-1.8. |
17 |
> |
18 |
> Question: is it OK to make dev-lang/ruby-1.8 PROVIDE rexml, yaml, etc.? e.g. |
19 |
> PROVIDE="dev-ruby/rexml dev-ruby/yaml dev-ruby/optparse" |
20 |
> Or will this cause problems? |
21 |
> |
22 |
|
23 |
It may not be considered 100% correct. More technically correct would |
24 |
be: |
25 |
|
26 |
PROVIDE="virtual/ruby-rexml virtual/ruby-yaml virtual/ruby-optparse" |
27 |
|
28 |
A few things however do provide similar to what you want, so maybe |
29 |
we should check with Nick/Daniel first. |
30 |
|
31 |
You should also remember that if it is a virtual (of whatever form), you |
32 |
will run into issues if you want to depend on specific versions ... |
33 |
|
34 |
|
35 |
Any reason not to keep 1.8.0 in testing for a bit, with whatever depends |
36 |
on it, and just specifying DEPEND as: |
37 |
|
38 |
DEPEND=">=dev-lang/ruby-1.8" |
39 |
|
40 |
? Then you can when they get marked stable just faze out the old ruby |
41 |
totally ... |
42 |
|
43 |
|
44 |
Regards, |
45 |
|
46 |
-- |
47 |
|
48 |
Martin Schlemmer |
49 |
Gentoo Linux Developer, Desktop/System Team Developer |
50 |
Cape Town, South Africa |