> Am 04.03.2015 um 13:04 schrieb Torsten Bergmann <asta...@gmx.de>: > > Phil wrote: >> Is it in 3.0 repo too? > > No, even when you copy it the #stable for 3.0 points to the old one > because I do not work with such an outdated Pharo version ;) > > You can try out and adopt to your needs, I use Pharo 4 already. > > Norbert wrote: >> are the *-Tests-* package for compatibility reasons for pharo 2? Otherwise >> they should be called *-Tests, right? > > No, I just follow the regular naming convention of Seaside packages here that > once was also agreed to > use for Pharo as well: https://code.google.com/p/seaside/wiki/PackageNaming > > It is used by Pharo (not on all places yet) and most projects (Glamour, GT, > Seaside, Bootstrap, Artefact, ... YouNameIt) and > MongoTalk should follow as well.
That is because monticello deals packages based on substring match. Should IMHO be changed in the not so far future. Norbert
