Lukas Renggli wrote: >>> Long answer: By renaming all the categories and protocols (this can be >>> automated using the OB-Refactoring and OB-Regex tools), creating a new >>> >> Would those support finding orphaned package extensions? Especially with >> removing stuff and reorganizing we will have that need occasionally. >> > > No, but the following remnant from the Seaside 2.9 packaging effort does: > > | packages | > packages := MCWorkingCopy allManagers > collect: [ :each | each packageInfo ]. > Smalltalk organization categories do: [ :cat | > (packages anySatisfy: [ :pak | pak includesSystemCategory: cat ]) > ifFalse: [ Transcript show: 'Category: '; show: cat; cr ] ]. > Smalltalk allClassesAndTraitsDo: [ :class | [ :cls | > cls organization categories do: [ :cat | > (packages anySatisfy: [ :pak | pak includesMethodCategory: cat > ofClass: cls ]) > ifFalse: [ Transcript show: 'Class: '; show: cls; show: > ' Protocol: > '; show: cat; cr ] ] ] > value: class; value: class class ] > > Lukas > Why why why is the default position of whoever wrote the above code to NOT contribute to the community? I dont get it. For me it would be the first thought that enters my mind... "perhaps someone else might find this useful".
That code if properly factored could easily go straight into MCWorkingCopy. It can do, the squeaksource.com/mc repo is open for contributions, and has been for a long time. Keith _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
