[Pharo-dev] Metacello: redefine a group for a platform to add an additional package

Sean P. DeNigris sean at clipperadams.com
Fri Nov 15 13:57:03 EST 2013

Tudor Girba-2 wrote
> Perhaps groups are not overridden for separate platforms

The version was referring to the wrong baseline. I uploaded a new config
which correctly loads the Platform package in Pharo 2.0...
- Fix Bug in v. 3.0.1
	- Refer to baseline 3.0.1
	- Declare Core package requires Platform on Pharo 2.0 <-- same behavior
when loading the default group, but would've failed to load Platform if
someone loaded Core explicitly

Also a small change to the version:
	spec package: 'SimplePersistence-Platform.pharo20' with:
'SimplePersistence-Platform.pharo20-SeanDeNigris.1' ].
	spec package: 'SimplePersistence-Platform' with:
'SimplePersistence-Platform.pharo20-SeanDeNigris.1' ].

>From the baseline:
	spec package: 'SimplePersistence-Platform' with:
sets 'SimplePersistence-Platform.pharo20' as the filename when one loads
#bleedingEdge, but the package name is still 'SimplePersistence-Platform'


View this message in context: http://forum.world.st/Metacello-redefine-a-group-for-a-platform-to-add-an-additional-package-tp4722109p4722545.html
Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

More information about the Pharo-dev mailing list