Avi Bryant <avi at beta4.com> wrote:
> The other motive is that I wanted a Squeak image that could monitor the
> repository directories and send out notification emails when new versions
> appear.  
Nice..

> ViewMC in fact grew up around the configuration interface for
> this tool (and if you want to receive commit emails for any repository on
> sqf.org, let me know and I'll add you).
Yes, actually put me in for all of them, filtering is easy. 

> > One thing I'm thinking of doing is saving the MC tools state in a file -
> > instead of recreating the repositories/packages in each new image, save
> > em and load them by default.
> 
> Yup, I've thought about that too.
> 
> > Another thing which I'd like but am not sure whats the best way to do is
> > "open new versions" - suppose I'm working on Refactory, and I know there
> > are two other people that have MC repositories where they occaisonally
> > post patches. Would be nice to have an option that sees what their most
> > recent work is, and for each package that isn't among my versions'
> > ancestors, shows it in a list.
> >
> > I'm still not at the point where I really need it, because I don't have
> > a high-turnaround collaborative project, but I do see the need for it.
> 
> Yeah, that would be nice.  One thing standing in the way of this is that
> HTTP and FTP repositories have no good way of delivering just the
> VersionInfo - you have to download the whole version.  So to find out
> anything about ancestry you have to grab the entire .mcz files from all of
> those repositories.  Maybe this isn't *that* big a deal, but it's a bit
> annoying.
> 
> One thing to play with would be to save two files for each version - a
> .mcz file that was complete, and a .mci file that just contained the
> version info.  Or I wonder if it's possible to use the byte-range
> extensions to HTTP to grab just the appropiate chunks of the ZIP file?
I'm not sure what happens when I open a remote version - is it cached?
what IS the "cache" repository type, now that I think of it? I was just
thinking that for heavy users, loading all remotely generated versions
of packages they're interested in is not that big a deal, as long as old
version are cached. Then the obvious next optimization after this
becomes too heavy seems to be marrying ViewMC with a format for patches
+ ancestry info, so that I'd ask ViewMC for patches for each version out
there compared to my latest released, and it would have all the
information needed to send me something nice and compact.

But I see no rush to do the optimization...

Daniel