How to submit refactorings (or: Removing PWS)

goran.hultgren at bluefish.se goran.hultgren at bluefish.se
Fri Nov 15 09:05:36 UTC 2002


Ned Konz <ned at bike-nomad.com> wrote:
> On Thursday 14 November 2002 01:38 pm, danielv at netvision.net.il wrote:
> > 3. After some testing, and sometime for the package maintainership
> > to move to SM, the removal script is made into an update.
> 
> I think we need to separate these removals somehow from the update 
> stream. Perhaps my earlier suggestion about having removal scripts 
> register themselves separately so you could choose to remove specific 
> packages.
> 
> I don't want someone who's using (say) PWS to update for bug fixes and 
> suddenly find themselves without functionality they needed...

I would say that a removal update should alert the user to the fact that
the package is being removed but that it can be easily installed from SM
- "Hey, this update removes PWS from the image. After the removal, would
you like to immediately reinstall it as a package from SqueakMap?".

Or something similar to that.

regards, Göran




More information about the Squeak-dev mailing list