It is possible to do platform-specific configurations within the same configuration. For GLASS, I generate the following attributes:
#'gs2.4.x' #'gs2.3.x' #'gs2.x' #'gs3.x' So that I can specify different package versions based on which underlying version of GemStone is running. A similar approach could be followed for Pharo.... Dale ----- "Stéphane Ducasse" <[email protected]> wrote: | It would be nice to have one per version | Pharo1.0 | Pharo1.1 | | May be people should use this convention in file names? | | Stef | | On Dec 8, 2009, at 3:04 AM, Esteban Lorenzano wrote: | | > Hi, | > I created the project MetacelloRepository as a centralized | repository | > for meta-packages, and started uploading metacello configurations. | > | > MCHttpRepository | > location: 'http://www.squeaksource.com/MetacelloRepository' | > user: '' | > password: '' | > | > Currently, I uploaded three projects: | > | > 1) ConfigurationOfFFI | > 2) ConfigurationOfSqueakDBX | > 3) ConfigurationOfGlorpDBX | > | > The whole idea of this is to have a project catalog working (like | > apt-get), so I encourage you to use it! | > | > The tools to manage on a fashion way this repository are comming, | > please be patient :) | > | > 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
