PetitParser on SmalltalkHub

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

PetitParser on SmalltalkHub

Nicolas Anquetil

In the process of loading Moose on Pharo 2.0, we had to update the
ConfigurationOfPetitSQLParser to add Pharo 2.0

ConfigurationOfPetitSQLParser>>development: spec
     <symbolicVersion: #development>
     spec for: #'pharo1.3.x' version: '1.0-baseline'.
     spec for: #'pharo1.4.x' version: '1.1-baseline'.
     spec for: #'pharo2.x' version: '1.1-baseline'.

But I cannot commit the change ...
Other solution would be to change the config Of moose to not load the
developement version, but it's not the best solution

nicolas

--
Nicolas Anquetil -- RMod research team (Inria)

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: PetitParser on SmalltalkHub

stephane ducasse
I do not understand why you cannot?
You are member of the Moose Team so it should work.
On Feb 22, 2013, at 11:48 AM, Nicolas Anquetil <[hidden email]> wrote:

>
> In the process of loading Moose on Pharo 2.0, we had to update the ConfigurationOfPetitSQLParser to add Pharo 2.0
>
> ConfigurationOfPetitSQLParser>>development: spec
>    <symbolicVersion: #development>
>    spec for: #'pharo1.3.x' version: '1.0-baseline'.
>    spec for: #'pharo1.4.x' version: '1.1-baseline'.
>    spec for: #'pharo2.x' version: '1.1-baseline'.
>
> But I cannot commit the change ...
> Other solution would be to change the config Of moose to not load the developement version, but it's not the best solution
>
> nicolas
>
> --
> Nicolas Anquetil -- RMod research team (Inria)
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: PetitParser on SmalltalkHub

stephane ducasse
In reply to this post by Nicolas Anquetil
You should be able to commit.
Is it fixed?

Stef


On Feb 22, 2013, at 11:48 AM, Nicolas Anquetil <[hidden email]> wrote:

>
> In the process of loading Moose on Pharo 2.0, we had to update the ConfigurationOfPetitSQLParser to add Pharo 2.0
>
> ConfigurationOfPetitSQLParser>>development: spec
>    <symbolicVersion: #development>
>    spec for: #'pharo1.3.x' version: '1.0-baseline'.
>    spec for: #'pharo1.4.x' version: '1.1-baseline'.
>    spec for: #'pharo2.x' version: '1.1-baseline'.
>
> But I cannot commit the change ...
> Other solution would be to change the config Of moose to not load the developement version, but it's not the best solution
>
> nicolas
>
> --
> Nicolas Anquetil -- RMod research team (Inria)
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: PetitParser on SmalltalkHub

Tudor Girba-2
Hi Stef,

This was also about the old repository from squeaksource. It should be ok now with SmalltalkHub.

Cheers,
Doru


On Feb 26, 2013, at 9:37 PM, stephane ducasse <[hidden email]> wrote:

> You should be able to commit.
> Is it fixed?
>
> Stef
>
>
> On Feb 22, 2013, at 11:48 AM, Nicolas Anquetil <[hidden email]> wrote:
>
>>
>> In the process of loading Moose on Pharo 2.0, we had to update the ConfigurationOfPetitSQLParser to add Pharo 2.0
>>
>> ConfigurationOfPetitSQLParser>>development: spec
>>   <symbolicVersion: #development>
>>   spec for: #'pharo1.3.x' version: '1.0-baseline'.
>>   spec for: #'pharo1.4.x' version: '1.1-baseline'.
>>   spec for: #'pharo2.x' version: '1.1-baseline'.
>>
>> But I cannot commit the change ...
>> Other solution would be to change the config Of moose to not load the developement version, but it's not the best solution
>>
>> nicolas
>>
>> --
>> Nicolas Anquetil -- RMod research team (Inria)
>>
>> _______________________________________________
>> Moose-dev mailing list
>> [hidden email]
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
www.tudorgirba.com

"Things happen when they happen,
not when you talk about them happening."


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev