[Pharo-project] How to correctly remove a package for everywhere?

Fernando Olivero fernando.olivero at usi.ch
Wed Jun 20 18:18:44 EDT 2012


Seems that removing a package does not imply removing the included
classes?Maybe this should be changed?

With RPackage is understandable, since its just a layer on top of the
system.You have to explicitly register/deregister packages.

Fernando


On Wed, Jun 20, 2012 at 10:24 PM, Mariano Martinez Peck
<marianopeck at gmail.com> wrote:
> well, I don't know what the hell happened, but a workaround I think it is
>
> DataStream removeFromSystem.
> RPackageOrganizer  default unregisterPackageNamed: #'System-Object Storage'.
>
> On Wed, Jun 20, 2012 at 10:19 PM, Mariano Martinez Peck <marianopeck at gmail.com<mailto:marianopeck at gmail.com>> wrote:
> So removing 'System-Object Storage' didn't work. I did:
>
> ScriptLoader new deletePackageNamed: 'System-Object Storage'.
>
> Now the MCWorkingCopy is removed (I don't see the package in Monticello Browser), but I can still browse the class DataStream, and the package is available from Nautilus.
>
> Now if I do:
>
> RPackageOrganizer  default unregisterPackageNamed: #'System-Object Storage'
>
> I don't see the package in Nautilus, but the class "DataStream" is still alive. I can do "DataStream name -> #DataStream" ..et...when I browse it with Nautilus I don't see the class but the category _UnpackagedPackage..
>
> so...how the hell can I remove this package and class from everywhere in the system?
>
> thanks
>
> --
> Mariano
> http://marianopeck.wordpress.com
>
>
>
>
> --
> Mariano
> http://marianopeck.wordpress.com
>




More information about the Pharo-dev mailing list