mercurial "flat checkout / update"

[rupert THURNER]

On Sat, Feb 13, 2010 at 21:16, Dirkjan Ochtman <dirkjan at ochtman.nl> wrote:

> On Sat, Feb 13, 2010 at 19:53, rupert THURNER <rupert.thurner at gmail.com>
> wrote:
> > yes, but for using push/pull we need to clone the repository, which we
> > wanted to avoid in a software distribution environment. what we intended
> to
> > have:
> >
> > 1. a slim client to update the software, e.g. mercurial
> > 2. which can be used to update a directory to a given revision
> > 3. as this directory is big (~1GB) and contains binaries, and no
> >     push/change from the client to the server is neither necessary nor
> >     desired we wanted to avoid having a cloned repository
> >
> > i know that one can export a whole revision without getting the .hg. but
> i
> > am unaware of something which stores the current revision and only
> delivers
> > the changed files between the current and the desired revision.
>
> So you want rsync, not Mercurial.
>
>
hehe ... yes that was also our first idea :)
as users should be able to upgrade and downgrade to specific versions, this
would mean we would have to externalize dedicated versions onto the server
filesystem. then the client as well needs to point to the correct directory.
which complicates it compared to issueing some hg command with the correct
tag or -r parameter.

rupert
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20100213/b8f99abc/attachment.html>