Chris

There are several points:

- we will maintain compatibility when filein/out using *

- now I was not aware that the class extensions should be lower case.

- Pharo should clean the packages because some of the extensions are for packages not existing anymore

and other edge cases.

Stef

On Fri, Jan 31, 2014 at 3:57 AM, Torsten Bergmann <astares@gmx.de> wrote:

Now that Pharo uses real packages beside categories I see some
lowercase "ghost" packages in Monticello Browser list after loading Seaside.

To reproduce just load Seaside using config browser and check in
Monticello browser.


I guess this is coming from methods in lowercase extension
categories like "*seaside-pharo-core" which do not really
match "Seaside-Pharo-Core" package.

Any comments?

Using a star (*) and all-lowercase method category names has been the 
convention for PackageInfo / Monticello for method extensions since 
the beginning (that is, for many many years now).

You'll undoubtedly run into this several more times - at least you will when bringing in older Monticello packages or those created outside of Pharo.  Not all, but some.

 

-cbc

Thx
T.