Marcus, I know about this issue; I asked the lead developers and they said that theres never been a real need for hg archive to work on remotes. Python isn't my persuasion so I never tried to tackle that issue. There is some clever ways you can stream the hg archive output from a remote ssh session, but this only works over ssh. There is another way from the hgweb interface you can download a tarball etc and achieve the same effect. Point is, remote export is possible but you'd have to treat each protocol differently and this really really belongs in mercurial and not an external lib which deals with the idiosynchrosies of the scm :) So I say either submit a patch to mercurial and fix it the right way, or just deal with using remote_cache like me :) anything else would be a major hack.
--matt PS. i'm including the verbose and user bits of code in the scm i just released to the mailing list ok? I assume that this is ok. view the project at http://tackletechnology.org/oss/cap2-mercurial . On 16 May, 01:16, "Marcus Ahnve" <[EMAIL PROTECTED]> wrote: > Hi all, > > I am writing a Mercurial plugin for Capistrano, and realized that 'hg > archive' only works for local repositories. What is the reason for > this? > > Cheers /Marcus > > --http://marcus.ahnve.net --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
