[squeak-dev] Deprecate update stream?

Nicolas Cellier nicolas.cellier.aka.nice at gmail.com
Sun Nov 24 21:11:56 UTC 2013


What is the last time this code were used? 3.8 image?
The clean way is to isolate a package then remove it (if we think that code
has an interest and could be revived).
Otherwise, the fast way is to just remove...


2013/11/24 Frank Shearar <frank.shearar at gmail.com>

> Utilities' "fetching updates" category seems obsolete - that's all the
> bits to work with an update stream, isn't it?
>
> If we want to continue with infrastructure for an update stream, why
> don't we put all this stuff together in its own package? Especially,
> can we pull the state out of Utilities? UpdateDownloader and
> UpdateUrlLists belong together in a separate object.
>
> It's not just Utilities though - I've seen a whole bunch of methods
> all over the place (he says not bothering to go find all those places)
> that look like they deal with update streams. These could also go into
> this new package.
>
> It ought to be the work of a few hours, for someone keen to improve
> the state of affairs!
>
> frank
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20131124/aae0921d/attachment.htm


More information about the Squeak-dev mailing list