[squeak-dev] Monticello automated duplication repository thing

Chris Muller asqueaker at gmail.com
Thu Sep 9 23:46:32 UTC 2021

Hi Tim,

I assume you keep your local copies of repositories which you work on.  For
those you don't, the package-cache is your automatic backup for unexpected
failures and/or offline work.  Propagation of versions to other
repositories is probably best done selectively, therefore manually, based
on the purpose of that repository (for example, you may want only release
versions out on squeaksource.com instead of all versions).  You could
probably easily engineer saving to a MCRepositoryGroup, but if you think
you want every single Version replicated in another repository -- that
sounds like backup, and so a real and actual backup solution might be what
you _really_ want.

 - Chris

On Wed, Sep 8, 2021 at 2:55 PM tim Rowledge <tim at rowledge.org> wrote:

> One fun issue of working remotely with a monticello repository on the
> other side of the world comes when something messes up the connection -
> power, network issues, war, asteroid strike, the usual things. Sure, we
> have the very local package-cache as a backup of sorts but given how easy
> it is to run a local SqueakSource instance it would be nice to have a way
> to to use it as a smart buffer to the 'real' repository, or maybe have
> repository types that have two (or more) outputs, whatever.
> Some googling suggests a few other people have been interested in the
> general idea but I didn't spot any solutions suggested. Before I burn any
> brain cells on it, has anyone actually worked on this?
> tim
> --
> tim Rowledge; tim at rowledge.org; http://www.rowledge.org/tim
> Useful random insult:- A gross ignoramus -- 144 times worse than an
> ordinary ignoramus.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20210909/7f4f58c1/attachment.html>

More information about the Squeak-dev mailing list