[squeak-dev] immovable MCConfigurations?

David T. Lewis lewis at mail.msen.com
Thu Oct 10 20:59:28 UTC 2013


For purposes of testing, perhaps you can hack MCHttpRepository>>location:
so that it passes the location string through a translation to
copyReplaceAll: 'source.squeak.org' with: 'box4.squeak.org:8888'.

Dave

On Thu, Oct 10, 2013 at 03:02:57PM -0500, Chris Muller wrote:
> I've been working on improving new-trunk at box4.squeak.org:8888/trunk.
> 
> Updates are now automatically copied every hour, on the hour, from
> source.squeak.org/trunk.  So we have a backup of trunk that also
> supports the new origin and history functions.
> 
> Now I want to start updating from box4.squeak.org:8888/trunk.  I set
> my "Update URL" in Preferences, but since the .mcm files specify the
> repository locations, it ends up updating from those places (e.g.,
> source.squeak.org).
> 
> How can I perform my update test?  How could we "move trunk" if it's
> URL ever changed?
> 
> Some ideas I've been tossing around:
> 
>   - Let any MCRepository be temporarily "overridden".  Others have
> expressed interest in doing this before for other reasons.
>   - Change McmUpdater to always use the Preferences defaultUpdateUrl
> instead of the one embedded in the MCConfiguration objects.  What IS
> the purpose of a MCConfiguration knowing its "repositories" anyway?
>   - Make the 'location' of a HttpRepository some sort of value-holder
> so the string could be udpated in one place?
>   - Run a batch script to update all the Configs at box4 to point to
> box4 instead of source.squeak.org?


More information about the Squeak-dev mailing list