| 1 |
On Sat, 2012-11-24 at 15:30 +0100, Theo Chatzimichos wrote: |
| 2 |
> Hello, |
| 3 |
> |
| 4 |
> We currently have values like the following: |
| 5 |
> RUBY_TARGETS="ruby19" |
| 6 |
> PHP_TARGETS="php5-3" |
| 7 |
> PYTHON_TARGETS="python2_7" |
| 8 |
> |
| 9 |
> I find it confusing, and I would like to propose to keep the same style for all |
| 10 |
> the above values. I personally prefer the ruby one. |
| 11 |
> Keep in mind that if the relevant teams decide to migrate to some other style, |
| 12 |
> it needs an announcement and migration plan. |
| 13 |
> |
| 14 |
> Theo |
| 15 |
|
| 16 |
|
| 17 |
+1 for the idea, |
| 18 |
|
| 19 |
but: |
| 20 |
|
| 21 |
I think format should be python2_7, a simple replace('_', '.') produces |
| 22 |
the correct version string. If need be it can be extended to minor |
| 23 |
versions |
| 24 |
2_7_3 to get 2.7.3 |
| 25 |
|
| 26 |
For ruby19, split in the middle to get 1.9, but what about 110, is it |
| 27 |
11.0 or 1.10. |
| 28 |
|
| 29 |
For php5-3, what happens if a future package has a digit as part of it's |
| 30 |
name which is allowed and are in the tree. It looks too much like php5 |
| 31 |
dash version 3 |
| 32 |
-- |
| 33 |
Brian Dolbec <dolsen@g.o> |
Archives