| 1 |
* Jim Ramsay <i.am@×××××××××.com> wrote: |
| 2 |
|
| 3 |
<snip> |
| 4 |
|
| 5 |
> Then you could do: |
| 6 |
> |
| 7 |
> >=dev-db/mysql-4.2 |
| 8 |
> |
| 9 |
> This would allow any mysql-4.1.*, including 4.1.20-r1 and 4.1.99 |
| 10 |
> |
| 11 |
> Though you do raise a good point... it would be nice to specify a "real |
| 12 |
> upstream version number" differently from the Gentoo "interim release |
| 13 |
> number" such as -r2. Can you think of a sane way to do that? |
| 14 |
|
| 15 |
Simply normalize the version numbers to a fixed amount of digit |
| 16 |
and use another one for gentoo's revisions ? |
| 17 |
|
| 18 |
I'm using 4 digits at my own buildsystem, but sometimes the upstream |
| 19 |
requires them all for itself, so we need some more, ie. 6 |
| 20 |
|
| 21 |
<snip> |
| 22 |
|
| 23 |
> Masking |
| 24 |
> >dev-db/mysql-4.1.20+ |
| 25 |
> should allow mysql-4.1.20-r1 but not mysql-4.1.21 |
| 26 |
|
| 27 |
"=dev-db/mysql-4.1.20.*" seems to be cleaner to me. |
| 28 |
|
| 29 |
Maybe |
| 30 |
|
| 31 |
"=dev-db/mysql-4.2.20" could be considered equal. |
| 32 |
|
| 33 |
|
| 34 |
cu |
| 35 |
-- |
| 36 |
--------------------------------------------------------------------- |
| 37 |
Enrico Weigelt == metux IT service - http://www.metux.de/ |
| 38 |
--------------------------------------------------------------------- |
| 39 |
Please visit the OpenSource QM Taskforce: |
| 40 |
http://wiki.metux.de/public/OpenSource_QM_Taskforce |
| 41 |
Patches / Fixes for a lot dozens of packages in dozens of versions: |
| 42 |
http://patches.metux.de/ |
| 43 |
--------------------------------------------------------------------- |
| 44 |
-- |
| 45 |
gentoo-user@g.o mailing list |
Archives