[Pharo-project] [update 1.2] #12217

Tony Fleig tony.fleig at gmail.com
Fri Oct 29 15:14:54 EDT 2010


It may not be perfect, but it certainly helps to understand why its like it
is.

Thanks,
TF

On Fri, Oct 29, 2010 at 2:27 AM, Marcus Denker <marcus.denker at inria.fr>wrote:

>
> On Oct 27, 2010, at 8:01 PM, Tony Fleig wrote:
>
> > In my Pharo core image there is indeed a Software Update entry under
> System, but when I select it a window pops up that says "0 new update
> file(s) processed."
> >
> > In my Seaside One-Click Image, there is no Software Update entry at all.
>
> -> only core images can be updated. Reason: updates do not cover packages
> managed outside (e.g. OmniBrowser, OCompletion). Yet the
> Core changes can make these packages not work anymore due to e.g.
> deprecation of code.
>
> -> Core images only load the updates of their release. that is, a 1.1 image
> loads updates for 1.1.1, but not for 1.2.
> Reason: You do not want to load experimental updates in a production
> system.
>
> All of this is far from perfect and should be improved.
>
>        Marcus
>
>
> --
> Marcus Denker  -- http://www.marcusdenker.de
> INRIA Lille -- Nord Europe. Team RMoD.
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/attachments/20101029/cf33af25/attachment-0001.html>


More information about the Pharo-dev mailing list