On Mon, Sep 20, 2010 at 9:18 PM, Hernán Morales Durand < [email protected]> wrote:
> Thanks for the reply Mariano, > > 2010/9/20 Mariano Martinez Peck <[email protected]>: > > > > > > On Mon, Sep 20, 2010 at 6:08 PM, Hernán Morales Durand > > <[email protected]> wrote: > >> > >> Hi Mariano, > >> > >> One thing I don't understand of Metacello is why don't you use > >> #latestVersion (or #latestReleaseVersion, #latestDevelopementVersion, > >> etc) instead of specifying the version number (e.g. '1.3'). How do you > >> keep updated about the latest version numbers? > > > > This is an excellent question :) > > > > In summary, there is a current problem with Metacello and Pharo: a user > of a > > project doesn't know which is the stable version for a pharo specifc > > version. For example, in this case suppose FFI 1.1 is the stable for > Pharo > > 1.0 and FFI 1.3 for Pharo 1.1. How can the user know that? there is no > easy > > solution. This is why Dale, me, stef, marcus, esteban, etc, have been > > discussed last week in ESUG. I will then send a summary about the > possible > > solution. > > > > Do I need to know the version numbers? > Depends on your needs. If you want to be able to recreate/reproduce it, then yes (at least right now). > > As an user I don't want to know the version number until extremely > necessary, i.e. I'm not switching everyday from 1.0 to 1.1 to 1.2 then > back to 1.1, etc. Eventually I try newer versions of Pharo to see what > I'm missing, and I choose to update acoordingly to the stability of > the whole set of packages concerning my application. It's not like I > evaluate the same "install base packages" script I've evaluated 6 > months ago :) > Ok, that's your use-case. OThers need exactly that :) > > By the way if you want to support internally the package status you > may try the Specifications pattern? > > > Anyway, if I use latestVersion, I am not sure you will load that again. > > I'm sure I will never load it again. Got it? :) > > yes. That's a use-case. Fortunatly Metacello is flexible enough to support both. Anyway, did you read my email about stable versions? I think that will clarify everything....since we will be able to use #stableVersion. Cheers Mariano > > Ok....I assumed he was using Pharo 1.1 (because is the current latest > stable > > release). Then, I KNOW that FFI 1.3 works well with Pharo 1.1. If he > takes > > the same image, and in 6 months someone releases FFI 1.4 that doesn't > work > > anymore with Pharo 1.1, then it will fail. > > > > Cheers > > > > Mariano > > > >> > >> 2010/9/20 Mariano Martinez Peck <[email protected]>: > >> > Hi Bruce. The recommended way to install external packages in Pharo is > >> > now > >> > using Metacello. > >> > > >> > To install FFI in Pharo, evaluate: > >> > > >> > Gofer new > >> > squeaksource: 'MetacelloRepository'; > >> > package: 'ConfigurationOfFFI'; > >> > load. > >> > > >> > ((Smalltalk at: #ConfigurationOfFFI) project version: '1.3') load. > >> > > >> > > >> > For more information about Metacello: > >> > > >> > http://code.google.com/p/metacello/ > >> > > >> > or you can see the talk we give with Dale last week at ESUG. > >> > > >> > Cheers > >> > > >> > Mariano > >> > > >> > On Sun, Sep 19, 2010 at 9:27 PM, Bruce Haugland > >> > <[email protected]> > >> > wrote: > >> >> > >> >> I noticed in Pharo 1.1 that the loadFFI script in the script loader > is > >> >> no > >> >> longer there. How can I load FFI into Pharo 1.1. I noticed that the > >> >> shared > >> >> library is there but that there are no supporting FFI Classes. > >> >> Thanks for the Help. > >> >> Bruce > >> >> _______________________________________________ > >> >> Pharo-users mailing list > >> >> [email protected] > >> >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users > >> >> > >> > > >> > > >> > _______________________________________________ > >> > Pharo-users mailing list > >> > [email protected] > >> > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users > >> > > >> > > >> > >> > >> > >> -- > >> Hernán Morales > >> Information Technology Manager, > >> Institute of Veterinary Genetics. > >> National Scientific and Technical Research Council (CONICET). > >> La Plata (1900), Buenos Aires, Argentina. > >> Telephone: +54 (0221) 421-1799. > >> Internal: 422 > >> Fax: 425-7980 or 421-1799. > >> > >> _______________________________________________ > >> Pharo-users mailing list > >> [email protected] > >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users > > > > > > _______________________________________________ > > Pharo-users mailing list > > [email protected] > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users > > > > > > > > -- > Hernán Morales > Information Technology Manager, > Institute of Veterinary Genetics. > National Scientific and Technical Research Council (CONICET). > La Plata (1900), Buenos Aires, Argentina. > Telephone: +54 (0221) 421-1799. > Internal: 422 > Fax: 425-7980 or 421-1799. > > _______________________________________________ > Pharo-users mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users >
_______________________________________________ Pharo-users mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users
