Danek Duvall wrote:
> Will we continue to keep the source tarballs in the gate, or will they be
> external? I know that mercurial has had performance problems with large
> binary blobs in the past; I don't know if they've been solved.
My plan is to transition as-is which yes, means keep the source tarballs
in the gate. I actually like that as I don't like having the build
possibly fail in the middle because it can't download something.
> Also note
> that as of now, there's no way to eradicate history, so all the old
> versions of things will stick around forever, even long past the time we've
> stopped caring, and people building current workspaces don't want to
> download stuff.
My view there is, if we reach a point where the workspace becomes too
big because of deletions that don't really delete, we could always
create a new workspace without them and switch to that, leaving the
old one around forever so old bits can be found and built if necessary
(and yes, it can be, I seem to be in teamware's deleted_files a lot).
If there are issues doing it this way then I am quite open to not doing
this transition now and allowing others to do it, so feel free :) I'm
just feeling pressure on this so thought I'd give it a shot, but I'm
not in a hurry there are bugs to fix as well.
Mike
