[Release] Philosophical Discussion - The updates button is useless - discuss

[Igor Stasenko]

2009/7/8 Andreas Raab <andreas.raab at gmx.de>:
> Igor Stasenko wrote:
>>
>> Now think, a third party maintains own set of mutated stuff, based on
>> 3.12 + extra stuff.
>> Obviously a user of such image , by pressing an 'update' button wants
>> to get an update in 3.12 branch + extra stuff updates.
>> What you think, is such approach makes sense?
>
> To be honest, I think it doesn't make too much sense, but it is very easy to
> support. Currently the update button in trunk is hooked up via:
>
> MCMCMUpdater updateFromRepositories: #(
>  'http://source.squeak.org/trunk'
> ).
>
> There are two trivial ways to extend this. First is provide a list of
> repositories that you'd like to update from:
>
> MCMCMUpdater updateFromRepositories: #(
>  'http://source.squeak.org/Squeak311' "fixes released for 3.11"
>  'http://squeaksource.com/Seaside29'  "current Seaside 2.9 updates"
>  'http://squeaksource.com/MyStuff'    "and whatever else"
> ).
>
This is good & simple up to the point, when the upstream updates (say 3.11)
going into conflict either with Seaside29
or MyStuff and breaking everything,  while most/rest of them is not.

So, by mentioning 'clever tools' i meant a more clever update process,
which can be expressed in a form:

UpdatesFrom:  'http://source.squeak.org/Squeak311'  revisedUnder: (
  UpdatesFrom: 'http://squeaksource.com/Seaside29'  revisedUnder: (
    UpdatesFrom: 'http://squeaksource.com/MyStuff' )) install

> Second, we could mark repositories directly in MC (i.e., "include in
> updates") and/or offer a menu option that just says "update from
> repository".
>
> Cheers,
>  - Andreas
> _______________________________________________
> Release mailing list
> Release at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/mailman/listinfo/release
>



-- 
Best regards,
Igor Stasenko AKA sig.