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 <stepharo@free.fr> 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
Moose-dev@iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

_______________________________________________
Moose-dev mailing list
Moose-dev@iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
_______________________________________________
Moose-dev mailing list
Moose-dev@iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev