Hi Adrian,
On 2010-03-17 11:15:10 -0300, Adrian Lienhard
<[email protected]> said:
Hi Esteban
Looks cool! I haven't had time to test it out in depth yet, but here
three questions:
- does it keep memory of which projects are loaded? Is this what you
refer to as "managed projects"?
Yes, it keeps a list of "managed projects" (with itself as the first
one) so it can check for new versions, etc.
- would it make sense to integrate it into Gofer?
I don't know... this is a "mixer" between Gofer and Metacello. If we
integrate it with Gofer core, suddenly we wil be creating a new
dependence package to add to core (Metacello)... of course, Metacello
can be loaded "at first project load" just like now "at first
configuration loaded", but I don't know if this is desirable... your
choice more than mine :)
What will be cool is to include the gofer project loader into PharoDev
distributions.
- 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.
Cheers,
Esteban
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
