Nautilus displays too many packages :)
We will have to fix that but ben is basically waiting for me to move on 
RPackage but I'm burnt on it.

Stef

On Aug 5, 2012, at 5:59 PM, GOUBIER Thierry wrote:

> Well, what happened is that I renamed a package in Nautilus (from X-B to X-C, 
> knowing there was already a X-A). It moved things from X-B to X-C, and 
> created X as well.
> 
> Now I erase X working copy on a regular basis (it's the Alt package you get 
> when you load Alt-Browser), noticing today thanks to the discussion that 
> RPackage was keeping a copy of Alt as well, so I unregistered it today. I 
> hope I finally got rid of it !
> 
> Thierry
> 
> ________________________________________
> De : [email protected] 
> [[email protected]] de la part de Stéphane Ducasse 
> [[email protected]]
> Date d'envoi : dimanche 5 août 2012 17:47
> À : [email protected]
> Objet : Re: [Pharo-project] About the migration from PackageInfo to RPackage
> 
> On Aug 5, 2012, at 2:54 PM, GOUBIER Thierry wrote:
> 
>> Is this the reason why when I built my package tree in the AltBrowser, I get 
>> four packages (X, X-A, X-B, X-C) but X contains all the classes of X-A, X-B 
>> and X-C ?
> 
> Which package classes?
> because MC use a pattern matching based on category names and explicitly 
> MCworking copy
> 
> So if you declare an MC package we name X and X-A indeed you are in trouble.
> The point with RPackage is to avoid the pattern matching approach of MC and 
> to get rid of the scan of all categories.
> 
>> Is this the reason why, in the current Alt-Browser packages, there is an 
>> auto-creation of an Alt package when you load it ?
>> 
>> I also get confused by the relation between class categories and packages. 
>> Is there a plan to get rid of class categories ?
> 
> yes
> 
>> At the moment, if you create then unload a package, the system categories 
>> stay behind (Pharo 2.0).
>> 
>> Thierry
>> ________________________________________
> 
> 
> 


Reply via email to