Re: [Monotone-devel] Packets or Packet I/O no longer works?

[Will Robertson]

Thanks, Clemens,
  Yes, I would be interested in seeing the TCL script, if only to avoid
having to work it all out myself!!

  Being able to send "patches" this way, that incorporate history, is
one of the main reason for me sticking with darcs (and I don't really
feel like debating any other pros or cons just at the moment);  I'm
afraid having to rely on full network access for sync'ing multiple
repositories is a bit of a show-stopper for me.
  Even Git seems promising in this regard, in-as-much as it's just a
bunch of files, and rsync is just a file-transfer mechanism.


On Wed, 2005-04-27 at 17:44 +0200, address@hidden wrote:
> 
> On 27 Apr, Will Robertson wrote:
> > This may be a silly question, but I can't seem to find any info. on
> 
> It isn't silly at all ...
> 
> > the Mailing List about how to use Packet I/O to copy the contents
> > (or changes since a certain date, etc) into a dump-file, such that
> > you can take it via sneaker-net to another machine and upload to
> > another Monotone repository.
> 
> I had exactly the same problem. Unfortunately the packet mechanism is
> only rudimentary since introduction of the Netsync protocol.
> 
> You can still dumping a single revision, manifest, all certs of a
> revision or a certain file using Monotones commands 
> 
>    certs fdata fdelta mdata mdelta rdata
> 
> > This is quite important to me, as I there's no way for me to access
> > a netsync server from one of the repositories.
> 
> I have written a small Tcl module for accessing a Monotone repository
> and a Tcl script using this module that enable me to dump the full (or
> delta) contents using Packet I/O between to arbitrary revisions. I use
> this to dump a certain state, sending that packets via email to home
> and import it via 'read' into my second repository.
> 
> The script is not very sophisticated, but it works for me. Perhaps it
> could be of any usage for you? I am currently thinking about wrapping
> it into a Starkit (or Starpack) to make a standalone out of it.
> 
> Let me know, if you would like to try it out. But please do not expect
> any warranty or comprehensive documentation ;-)
> 
> 
> Ciao,
> Clemens.
> 
> PS: Unfortunately, the re-importing repository needs to contain the
>     whole history of the revision(s) you are importing via Packet I/O,
>     as Monotone does not read-in any version, whose ancestor it
>     doesn't already contain ... :-(
>