> On 2021-09-09, at 4:46 PM, Chris Muller <asqueaker at gmail.com> wrote:
> I assume you keep your local copies of repositories which you work on.  

Well, they are kept by the system but I don't treat them specially. Apart from anything else I don't work on only one machine, so it doesn't make a very good organised archive. Also, that's *all* the packages I might touch, which is a different sort of cache to what I'm considering.

> 
> 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 

What I have is work stuff that nominally goes to a repository on the other side of the continent, where sometimes the power and network don't  co-operate. All the commits I make to that repository ought to get there PDQ but sometimes don't. My thought is to make a variant that allows me to have a local squeaksource system that I publish to, and that automagically passes those on to the 'real' system, handling failures etc. When I refresh my view, it should in turn refresh from the remote system and then show me the updated collection of packages.

I'm sure there are many ways to tackle this.

tim
--
tim Rowledge; tim at rowledge.org; http://www.rowledge.org/tim
Useful random insult:- His seat back is not in the full upright and locked position.