On 07/14/2010 10:34 AM, Hyrum K. Wright wrote:
> On Wed, Jul 14, 2010 at 2:53 PM, Noorul Islam K M <noorul_at_collab.net> wrote:
>> Hello all,
>> I am planning to implement the requirement mentioned in issue
>> http://subversion.tigris.org/issues/show_bug.cgi?id=3645. I hope no one
>> has yet started on this.
>> I am going to add an option "--archive" to export command. If specified,
>> the output of the export command will be in tar format. which will be
>> dumped to STDOUT. The user can pipe it to any other program thereafter.
>> For a user it will be like this.
>> $ svn export . --archive > /tmp/export.tar
>> $ svn export . --archive | bzip2 > /tmp/export.tat.bz2
>> Any valuable inputs will be helpful.
> I think issue #3645 is about compressing the backend storage, rather
> than some output of the svn client command.
Not sure what leads you to believe this. If you read the issue, you can
clearly see that it discusses 'git archive' (which is a tree export
mechanism, not a repository compression tool) and compares such with 'svn
export' as the lesser-but-at-least-somewhat-viable workaround.
That said, I too am less than thrilled about adding what amounts to Yet
Another Implementation Of the Tar Archive Algorithm to our codebase, and
still more disappointed to think that the minute we do this the Windows
users will be clamoring for Zip or 7z or something else.
I've closed issue 3645 as WONTFIX with a similar explanation (and a
recommended alternative feature that would be more generally useful).
C. Michael Pilato <cmpilato_at_collab.net>
CollabNet <> www.collab.net <> Distributed Development On Demand
Received on 2010-07-14 16:52:42 CEST