Ole Markus With wrote:
> Maybe I could change the currently masked php5-5 slot to php5_5 instead
> and then eventually phase our the hyphen based slots. This would mean
> inconsistency between the php slots for some time, but eventual
> consistency with Python, which I do see as a good thing.
I th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/24/2012 03:30 PM, Theo Chatzimichos wrote:
> Hello,
>
> We currently have values like the following: RUBY_TARGETS="ruby19"
> PHP_TARGETS="php5-3" PYTHON_TARGETS="python2_7"
>
> I find it confusing, and I would like to propose to keep the same
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 24/11/12 19:46, Mike Gilbert wrote:
> On Sat, Nov 24, 2012 at 1:36 PM, Diego Elio Pettenò
> wrote:
>> On 24/11/2012 10:19, Peter Stuge wrote:
>>> Diego, remember the original point. It is obvious that a
>>> common syntax is more coherent and thus
Peter Stuge wrote:
> Thinking out loud another round: _TARGETS is an interface by Gentoo,
> so maybe it would not be such a bad idea to use existing Gentoo
> identifiers there, ie. (a subset of?) PMS version specifications.
Including the package name. This would also make the UX change
smaller, bu
On 24/11/2012 11:20, Peter Stuge wrote:
> This discussion is not about how wise the RUBY_TARGETS syntax is for
> ruby, it is about if it would be possible to find and use a common
> syntax for all languages, to make a more consistent Gentoo interface.
Pffft...
>> We're not going to change it just
Jauhien Piatlicki wrote:
> > PHP_TARGETS="5.3 5.4"
> > RUBY_TARGETS="1.9"
> > PYTHON_TARGETS="2.7"
> >
> > But maybe it would be too problematic?
>
> What will you do with PYTHON_TARGETS="python2_7 python3_2 pypy1_9
> jython2_5" then?
That's an excellent point. Thanks!
Thinking out loud another
On 24/11/2012 10:40, Jauhien Piatlicki wrote:
> What will you do with PYTHON_TARGETS="python2_7 python3_2 pypy1_9
> jython2_5" then?
That's another good point. And since Ruby has been brought up before,
let's not forget that we're not really slotting just for the sake of it
most of the time.
JRub
On Sat, 2012-11-24 at 08:07 -0800, Diego Elio Pettenò wrote:
> On 24/11/2012 07:46, Brian Dolbec wrote:
> > For ruby19, split in the middle to get 1.9, but what about 110, is it
> > 11.0 or 1.10.
>
> Okay stop.
>
> There's no 1.10.
>
> There's 2.0 that's being developed for a long time.
>
>
On Sat, Nov 24, 2012 at 1:36 PM, Diego Elio Pettenò
wrote:
> On 24/11/2012 10:19, Peter Stuge wrote:
>> Diego, remember the original point. It is obvious that a common
>> syntax is more coherent and thus easier for the world to understand.
>> Having that would be a good thing. It is also obvious t
24.11.12 19:19, Peter Stuge написав(ла):
> Look at the following:
>
> PHP_TARGETS="php5-3"
> RUBY_TARGETS="ruby19"
> PYTHON_TARGETS="python2_7"
>
> Note the redundancy, which I'm not quite sure why we have at all..
>
> Why not also eliminate the language name in one of the two places;
> either i
On 24/11/2012 10:19, Peter Stuge wrote:
> Diego, remember the original point. It is obvious that a common
> syntax is more coherent and thus easier for the world to understand.
> Having that would be a good thing. It is also obvious that the ruby
> syntax is problematic in the general case.
And th
Diego Elio Pettenò wrote:
> On 24/11/2012 07:46, Brian Dolbec wrote:
> > For ruby19, split in the middle to get 1.9, but what about 110, is it
> > 11.0 or 1.10.
>
> Okay stop.
>
> There's no 1.10.
>
> There's 2.0 that's being developed for a long time.
>
> And we're not going to change our
On 24/11/2012 07:46, Brian Dolbec wrote:
> For ruby19, split in the middle to get 1.9, but what about 110, is it
> 11.0 or 1.10.
Okay stop.
There's no 1.10.
There's 2.0 that's being developed for a long time.
And we're not going to change our scheme just because of some
theoretical corner c
On Sat, 2012-11-24 at 15:30 +0100, Theo Chatzimichos wrote:
> Hello,
>
> We currently have values like the following:
> RUBY_TARGETS="ruby19"
> PHP_TARGETS="php5-3"
> PYTHON_TARGETS="python2_7"
>
> I find it confusing, and I would like to propose to keep the same style for
> all
> the above val
On Sat, 24 Nov 2012 15:30:07 +0100
Theo Chatzimichos wrote:
> Hello,
>
> We currently have values like the following:
> RUBY_TARGETS="ruby19"
> PHP_TARGETS="php5-3"
> PYTHON_TARGETS="python2_7"
>
> I find it confusing, and I would like to propose to keep the same style for
> all
> the above v
Hello,
We currently have values like the following:
RUBY_TARGETS="ruby19"
PHP_TARGETS="php5-3"
PYTHON_TARGETS="python2_7"
I find it confusing, and I would like to propose to keep the same style for all
the above values. I personally prefer the ruby one.
Keep in mind that if the relevant teams de
16 matches
Mail list logo
