> > and no, I didn't implement a project remove... because metacello (afaik) > doesn't have it, and it was outside the scope of the loader. Of course, I > think it is a very important feature, but it will be added in the future. > >
Remember the very known problem of the overrides (if there are). Cheers Mariano > Cheers, > Esteban > > > > On 2010-03-17 11:42:21 -0300, Alexandre Bergel <[email protected]> said: > > Hi Esteban, >> >> It looks cool. I tried and I was seen apparent problems. >> I think it would be useful to add >> loadLastVersionOf: >> loadLastStableVersionOf: >> >> I am not aware of Metacello details, but where is there a distinction >> between loading and upgrading? >> You do not have removeProject: or something? >> >> Cheers, >> Alexandre >> >> >> On 17 Mar 2010, at 09:23, Esteban Lorenzano wrote: >> >> Hi, >>> I want to announce the immediate release of GoferProjectLoader, a >>> Gofer extension to manage Metacello configurations. >>> For all who want to know quickly what is this, here is a small >>> synopsis: >>> >>> GoferProjectLoader is a loader for Metacello configurations (A >>> metacello configuration is a full project load tool, including >>> package/project dependencies with it corresponding versions). >>> GoferProjectLoader automatically scan projects stored on >>> MetacelloRepository, but you can add your private repositories as >>> well. GoferProjectLoader responsibilities include: >>> >>> 1) Install project versions and keep track of them. >>> 2) Update configurations and upgrade projects (if desired). >>> >>> GoferProjectLoader relies on Metacello and Gofer to perform this >>> tasks (In fact, It can be thought as a Gofer extension to understand >>> Metacello packages). >>> >>> To load GoferProjectLoader, you need to do: >>> >>> Gofer it >>> squeaksource: 'MetacelloRepository'; >>> package: 'ConfigurationOfGoferProjectLoader'; >>> load. >>> >>> ConfigurationOfGoferProjectLoader project lastVersion load. >>> >>> With this... you'll never need again to perform once and again this >>> repetitive configuration... instead, you can do things like: >>> >>> Gofer project >>> load: 'Seaside30'; >>> load: 'Pier2'. >>> >>> You can see the full documentation here: >>> http://www.smallworks.com.ar/en/community/GoferProjectLoader >>> >>> Now I'm working on the promised page for configurations (Adrian: I >>> really sorry for the delay... I know I promised this a lot of time >>> ago... but time is the tyrant :( ) >>> >>> Cheers, >>> Esteban >>> >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> [email protected] >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >> > > > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >
_______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
