now��� I think one of our problems is the use of #stable into configurations. I have expressed my concerns other moments, but here it is again:
Project A uses for instance Seaside stable which is, when Project A starts Seaside 3.0
time after owner tries to load Project A��� but since then stable from Seaside has move from Seaside 3.0, to 3.1.2
now��� that can be ���not desired��� at all.
Project A wanted Seaside 3.0, not 3.1 (of course, if using Semantic Versioning that will mean there is just changes to the API in a compatible way��� but we all know we do not use semver correctly almost never).
So��� in fact Project A cannot depend on Seaside/#stable��� instead, he should depend on Seaside/3.0 directly to be sure you have the version you want.
that of course introduces other kind of problems, like: what happens if I want to install Project A who depends on Seaside/3.0 and Project B who depends on Seaside/3.0.2
Well��� ideally, we need to be able to resolve those problems when loading.
Also, it would be cool to specify version dependencies as ���Seaside/3.*���, for instance��� but well��� that���s another thread :)
As you can see��� is not an easy task.
Esteban
Absence of Metacello won't help you dealing with dependencies
and loading stuff by using hand-made scripts by dozens of people
written at different points in time and not maintained by anyone.