Alex
I imagine that this is to avoid mistake like
Moose
Moose-X
Moose-Y
and that people do it
Moose-All
Moose-X
Moose-Y
If this is what you have in mind how would it work from a process
point of view
1- I create
Moose
2- I create
Moose-XXX
-> wanring
3- remove/rename
Moose -> Moose-All
then be able to create
Moose-XXX
This scenario would be realllllly important because we can really
screw up MC packges with overlapping packages
Scenario 2
1 - I have Moose
2- I load Moose-XXX
PS: if you want to have feedback from people, they should not know
what you are implying in advance like me.
On Oct 11, 2008, at 12:19 PM, Alexandre Bergel wrote:
Maybe we should forbid a package XXX-YYY to be required for a
package named XXX
What do you think?
A simple check will do it...
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
