So smallDude exhibits the same syndrom
I will probably introduce a configuration of FullMoose is for loading the top level products
and remove from Moose the dependencies to DSM and SmallDude because these cycles do not make sense
But it may break the default Moose so I will wait for your point of view.
Stf
On 27/6/14 22:58, stepharo wrote:
Hi
Usman found that mooseDSM depends on Moose and that Moose depends on DSM.
This shows a problem with the configurations in the Moose ecosystem.
After thinking about it, there are two kinds of configurations:
- first kind of a configuration should express the dependencies to systems that are mandatory.
- the second kind represents "Full project" configurations that express a complete "applications"
with all the subapplications. They do not express that the tool must all the dependencies to be resolved to work.
For example, MooseAlgos are in Moose even if we do not use MooseAlgos.
Such full project should not be referred too.
=> So we should distinguish such different configurations.
For example Glamour as a UI builder should not depend on Roassal
But Glamour as a full project can depend on Roassal.
Then at the Moose or project level we can decide what to load.
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