I now moved it into a separate package:

Name: Moose-RoassalPaintingsPackageBlueprint-TudorGirba.1
Author: TudorGirba
Time: 8 December 2013, 8:30:41.818698 am
UUID: d5aab308-867f-42f9-b022-9da1f77abeab
Ancestors: 

moved package blueprint in an explicit separate package to make it unloadable from Moose


On Sat, Dec 7, 2013 at 11:01 PM, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:


This whole Package Blueprint implementation should actually go away. The code is unmaintained and badly programmed.

ok so let us kill it
sadly because I would need it
but anyway nobody really understood that when you want to build modular system you need tools to analyse them.
We are focusing too much on publications but this is like that.

Stef



Doru


On Sat, Dec 7, 2013 at 7:44 PM, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
I get one package and select
Browse Package Blueprints

when I select incomings pane -> boum


packageForSurface: aSurface
        ^ aSurface anyOne packageScope

anyone leads to a bug.

Stef



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



--

"Every thing has its own flow"
_______________________________________________
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




--
www.tudorgirba.com

"Every thing has its own flow"