----- "Esteban Lorenzano" <[email protected]> wrote:
| > - any idea about how we go to differentiate "stable" and "unstable"
|
| > universes for each Pharo version? How does the user know which version
| > is the one he needs for his version of Pharo? Sorry, this is not
| > directly related to the Gofer Project Loader but I think it is the next
| > important step towards a working package management system!
|
| No clue... maybe we need to add to Metacello a new "dependence
| dimension", like "minimum version of distribution"... but Dale can be
| much more helpful than me in this area.
I imagine that code targetted for specific Pharo versions will be treated like
we treat code targeted for different Smalltalk dialects. So you would write
specs like the following:
spec for: #common do: [...].
spec for: #squeakCommon do: [...].
spec for: #pharo do: [...].
spec for: #'pharo1.0' do: [...].
spec for: #'pharo1.1' do: [...].
or possibly like the following, if a finer version granularity is needed:
spec for: #common do: [...].
spec for: #squeakCommon do: [...].
spec for: #pharo do: [...].
spec for: #'pharo1.0' do: [...].
spec for: #'pharo1.0-10508' do: [...].
spec for: #'pharo1.0-10515' do: [...].
spec for: #'pharo1.1' do: [...].
spec for: #'pharo1.1-11508' do: [...].
spec for: #'pharo1.1-11515' do: [...].
Dale
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
