+1. �Someone wanting something that "just runs" can/should do something like

�(MCPackage named: 'HelpSystem' ifNone:'[ DeafObject current ]) unload

Another approach is to trap and log errors so that a lengthy build process completes and then clearly shows where it encountered problems.

Bill


________________________________________
From: pharo-project-bounces@lists.gforge.inria.fr [pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of St�phane Ducasse [stephane.ducasse@inria.fr]
Sent: Thursday, January 06, 2011 6:11 AM
To: Pharo-project@lists.gforge.inria.fr
Subject: Re: [Pharo-project] why (MCPackage named: 'NonExistenPackage') unload. doesnt fail ?

> Do we want that? I am finding a lot of outdated code that uses code like that and it doesnt fail, but still doesnt unload the package.
>
> For example, cleanUpForRelease does a
> � � (MCPackage named: 'HelpSystem') unload.
>
> and that package doesnt exist anymore since it was split....
>
> so...do we want that silent behaviour ?

probably not.
Better fix the scripts as early as possible

>
> cheers
>
> mariano