Point one

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

Re: Point one

stepharo

On 28/6/14 12:01, Guillermo Polito wrote:
Just a thought, maybe offtopic, but that goes in the modularity path... What about adding also a new ´moose´ tab to the configuration browser showing only moose sub-products?

I think that if I would have got an engineer to work on the catalog distribution this process and infrasturcture could
used by any large projects and Moose could have use that. And indeed I have the same idea than you.

Stef



On Sat, Jun 28, 2014 at 11:55 AM, stepharo <[hidden email]> wrote:
SmallDude looks scary. The stable version is tagged as broken! Really cool :) and is just from 2011 :)
Now I cleaned it.


I kept the dependencies to
    spec project: 'Moose Core' with: '5.0-baseline'.
for now.


Stef


On 28/6/14 11:21, stepharo wrote:
So far we (Guillaume, christophe and me) addressed clean the mess and make sure that we can manage the following configuration with versionner

    XMLWriter
    XMLParser
    Pastell
    PhExample
    OrderPreserving
    BitmapCharacterSet
    HashTable
    Fame

We will probably ask christophe that versionner on release proposes the choice to use stable or the version.

    I will continue
    with

    Units
    MooseAlgoRubric
    SmallDude
    MetaNool
    Maggrite3

Now I will probably have to fork some configurations if I cannot publish on the repositories.

Stef
_______________________________________________
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



_______________________________________________
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: Point one

stepharo
In reply to this post by Stephan Eggermont-3
I will see.
I want simplification.
I will check the idea of the engines.
For now I'm cleaning all the configurations and making sure that they
can work with versionner.

Stef

On 28/6/14 12:43, Stephan Eggermont wrote:

> Steph, please try this with ConfigurationOfPharo first.
> You have much more control over that, and it will
> allow you to break the tools fast without bothering
> others. We use ConfigurationOfMoose.
>
>> When you develop you want to always get the latest (and certainly not on
>> project you have no control over).
> You want to, but you can't. And you definitely don't want
> to have to create all kinds of configuration versions of
> packages outside your control just to be able to load.
> I would like to include Torch. Doesn't work with latest.
>
> Cleaning up of moose configuration is much appreciated.
> You probably want to add some groups, so you can have your
> tools.
>
> Stephan
>
>  
>
>
>
>
>
>
> _______________________________________________
> 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: Point one

stepharo
In reply to this post by stepharo
added a stable and version to deepTraverser



On 28/6/14 11:21, stepharo wrote:

> So far we (Guillaume, christophe and me) addressed clean the mess and
> make sure that we can manage the following configuration with versionner
>
>     XMLWriter
>     XMLParser
>     Pastell
>     PhExample
>     OrderPreserving
>     BitmapCharacterSet
>     HashTable
>     Fame
>
> We will probably ask christophe that versionner on release proposes
> the choice to use stable or the version.
>
>     I will continue
>     with
>
>     Units
>     MooseAlgoRubric
>     SmallDude
>     MetaNool
>     Maggrite3
>
> Now I will probably have to fork some configurations if I cannot
> publish on the repositories.
>
> Stef
> _______________________________________________
> 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: Point one

DiegoLont
In reply to this post by stepharo
Stef, Guillaume and Christophe,

If you fix configurations, you must fix them properly.

I have reviewed 2 configurations now:
        XMLWriter is no longer valid for Pharo1.x
        XMLParser is no longer valid for Gemstone and does not have a correct development version.
So please revert all changes, because the way you do this now, will only create a lot of upset people.

Regards,
Diego

On 28 Jun 2014, at 11:21, stepharo <[hidden email]> wrote:

> So far we (Guillaume, christophe and me) addressed clean the mess and make sure that we can manage the following configuration with versionner
>
>    XMLWriter
>    XMLParser
>    Pastell
>    PhExample
>    OrderPreserving
>    BitmapCharacterSet
>    HashTable
>    Fame
>
> We will probably ask christophe that versionner on release proposes the choice to use stable or the version.
>
>    I will continue
>    with
>
>    Units
>    MooseAlgoRubric
>    SmallDude
>    MetaNool
>    Maggrite3
>
> Now I will probably have to fork some configurations if I cannot publish on the repositories.
>
> Stef
> _______________________________________________
> 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: Point one

stepharo
How do I know what is correct.

Stef

> Stef, Guillaume and Christophe,
>
> If you fix configurations, you must fix them properly.
>
> I have reviewed 2 configurations now:
> XMLWriter is no longer valid for Pharo1.x
> XMLParser is no longer valid for Gemstone and does not have a correct development version.
> So please revert all changes, because the way you do this now, will only create a lot of upset people.
>
> Regards,
> Diego
>
> On 28 Jun 2014, at 11:21, stepharo <[hidden email]> wrote:
>
>> So far we (Guillaume, christophe and me) addressed clean the mess and make sure that we can manage the following configuration with versionner
>>
>>     XMLWriter
>>     XMLParser
>>     Pastell
>>     PhExample
>>     OrderPreserving
>>     BitmapCharacterSet
>>     HashTable
>>     Fame
>>
>> We will probably ask christophe that versionner on release proposes the choice to use stable or the version.
>>
>>     I will continue
>>     with
>>
>>     Units
>>     MooseAlgoRubric
>>     SmallDude
>>     MetaNool
>>     Maggrite3
>>
>> Now I will probably have to fork some configurations if I cannot publish on the repositories.
>>
>> Stef
>> _______________________________________________
>> 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
>

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

Re: Point one

stepharo
In reply to this post by DiegoLont
I will check that after lunch.

> Stef, Guillaume and Christophe,
>
> If you fix configurations, you must fix them properly.
>
> I have reviewed 2 configurations now:
> XMLWriter is no longer valid for Pharo1.x
> XMLParser is no longer valid for Gemstone and does not have a correct development version.
> So please revert all changes, because the way you do this now, will only create a lot of upset people.
>
> Regards,
> Diego
>
> On 28 Jun 2014, at 11:21, stepharo <[hidden email]> wrote:
>
>> So far we (Guillaume, christophe and me) addressed clean the mess and make sure that we can manage the following configuration with versionner
>>
>>     XMLWriter
>>     XMLParser
>>     Pastell
>>     PhExample
>>     OrderPreserving
>>     BitmapCharacterSet
>>     HashTable
>>     Fame
>>
>> We will probably ask christophe that versionner on release proposes the choice to use stable or the version.
>>
>>     I will continue
>>     with
>>
>>     Units
>>     MooseAlgoRubric
>>     SmallDude
>>     MetaNool
>>     Maggrite3
>>
>> Now I will probably have to fork some configurations if I cannot publish on the repositories.
>>
>> Stef
>> _______________________________________________
>> 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
>

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