| 1 |
On 6/15/07, John R. Graham <n3440d@×××××.com> wrote: |
| 2 |
> I occasionally run across a package version dependency issue that cannot |
| 3 |
> be elegantly solved by the current dependency syntax. Every time I've |
| 4 |
> come across this, it's boiled down to a range. For example, package |
| 5 |
> some-cat/foo has the following versions in the tree |
| 6 |
> some-cat/foo-4.0.0-r2 |
| 7 |
> some-cat/foo-4.1 |
| 8 |
> some-cat/foo-4.1.1 |
| 9 |
> some-cat/foo-4.1.2-r2 |
| 10 |
> some-cat/foo-4.2.1-r5 |
| 11 |
> some-cat/foo-4.3 |
| 12 |
> some-cat/foo-4.4 |
| 13 |
> |
| 14 |
|
| 15 |
/me votes for rubyesqe range syntax |
| 16 |
|
| 17 |
some-cat/foo-( s:4.1 .. s:4.2) // start at slot 4.1 , and go upto |
| 18 |
and including 4.2 |
| 19 |
some-cat/foo-( s:4.1 ... s:4.2) // start at slot 4.1 and go upto, but |
| 20 |
not including 4.2 |
| 21 |
some-cat/foo-( v:4.1.0 .. v:4.2.0 ) // start at version 4.1.0 and go |
| 22 |
upto and including 4.2.0 |
| 23 |
some-cat/foo-( v:4.1.0 ... v:4.2.0 ) // start at version 4.1.0 and go |
| 24 |
upto , but excluding 4.2.0 |
| 25 |
|
| 26 |
I know thats probably not possible in a bash env tho, but hopefully |
| 27 |
the 'range' concept will give some inspiration, as IMO, having to |
| 28 |
specify the ebuild atom name for both upper and lower values is |
| 29 |
redundant, and easily missused as lamented by Vlastimil Babka |
| 30 |
|
| 31 |
/me hides in his corner to avoid abuse from people despising ruby lovers |
| 32 |
|
| 33 |
/me goes and joins ruby addicts anonymous |
| 34 |
|
| 35 |
-- |
| 36 |
Kent |
| 37 |
ruby -e '[1, 2, 4, 7, 0, 9, 5, 8, 3, 10, 11, 6, 12, 13].each{|x| |
| 38 |
print "enNOSPicAMreil kdrtf@×××.com"[(2*x)..(2*x+1)]}' |
| 39 |
-- |
| 40 |
gentoo-dev@g.o mailing list |
Archives