You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@gump.apache.org by Stefan Bodewig <bo...@apache.org> on 2004/03/01 17:27:04 UTC
Re: Gump Sync
On Mon, 1 Mar 2004, Adam R. B. Jack <aj...@trysybase.com> wrote:
> I do think we need our own rsync, but it is good to know of gotcha
> like this prior to writing it.
Quite possible. In particular we don't need rsync but just sync.
> Do we need/want the .cvsignore functionality?
I don't really think so.
I just now looked into my build.sh again and we don't use -C. Now you
have me extra puzzled, since it behaves exactly as if the switch was
enabled (and I don't think -a includes -C).
Anyway, we should use a complete sync without any excludes IMHO.
> I suspect we wish to migrate a directory based off existence and
> timestamp, but not contents (we ought rely upon timestamps, no?).
This will probably be good enough for us.
> What to do in case of failure? Just bail at time of issue, or ought
> we attempt to unwind our changes [not likely].
For our purpose a failure isn't as dramatic as for say mirrors.
Making big noise is warranted, but the orginal contents are still
there, so I wouldn't invest too much time into rollback support.
> Sync is likely to get hit with disk full, since many of the other
> aspects of Gump are change in place.
Sync deletes the previous build results, so I think it's less likely
to be hit by disk space issues than the actual build process.
> Ought we keep a track of all we do, so we can report upon that for
> users? [We capture output of CVS/SVN which ought be the same, but
> it might be nice for us to do similarly.]
Some kind of human readable lock would be nice.
> Ought we design this via the Wiki?
Why not?
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: Gump Sync
Posted by "Adam R. B. Jack" <aj...@trysybase.com>.
> I just now looked into my build.sh again and we don't use -C. Now you
> have me extra puzzled, since it behaves exactly as if the switch was
> enabled (and I don't think -a includes -C).
I should have said that didn't quite register (but didn't 'cos I didn't have
time to check). I didn't think Gumpy set that. Still, I've seen rsync just
not clean up directories that it ought, a long ways back (and can't recall
details). I just don't trust it.
> Sync deletes the previous build results, so I think it's less likely
> to be hit by disk space issues than the actual build process.
Yeah, good point -- I was wrong. It was creating xdocs (for a new project)
that dorked when LSD became full.
regards
Adam
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org