On Mardi, nov 18, 2003, at 16:09 Europe/Zurich, 
goran.krampe at bluefish.se wrote:

> What I wrote. :) Again, I think it would be a mistake putting it inside
> the release because it will just get more fragile. We have the map that
> keeps all these entities at our fingertips - why would we need to put
> anything inside the package?

goran the point is that you can have a different versioning rate
for package and their config map still the config maps can be associated
with their package.

	Hence we can wirte
		((PackageStef version: 3.3) withConfigNamed: 'stef3') load
		((PackageStef version: 3.3) newConfigMap: (ConfigMap new: {packg1-> 
3.4 . pakg2 -> 3.3a}) submit
		and
		still

		xxxxx  versionAs: 3.4 withConfigNamed: 'default'

I see the point of markus and your point. Flexibility does not mean 
that you have
a completely separate entities.

stef