[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: how to integrate a zip based archive into svn

From: Nico Kadel-Garcia <nkadel_at_gmail.com>
Date: Sun, 18 Oct 2015 04:40:31 -0400

On Sun, Oct 18, 2015 at 4:09 AM, Eckard Klotz <eckard.klotz_at_t-online.de> wrote:
> Hello All.
> My question is associated with setting up a new SVN archive for an old
> project without loosing the old file-versions.
> Even I'm programming for nearly 20 years and have a open source project for
> nearly 10 years I'm new in SVN. Until now I have archived my project by
> zipping my source folder.
> Now I wonder if there is a way supported by SVN to transfer every zip file
> as one revision into a new fresh SVN archive. It is clear to me that this
> will not contain the automatic creation of comments. But having a archive
> that contains the historical files and that allows me to step back to
> earlier revisions would be helpful.
> Best regards,
> Eckard Klotz

You sound like my old friend Crash, who wrote the CRM114 spam
filtering software. He has much more faith in a USB drive in his own
hands than in a remote source control system,

There's no reason you can't make a local copy of all zip files in a
local working copy, and check that in. I think you'd be in much better
shape if you bothered to unzip the first one, commit that to master,
make a tag, delete the local copy, unzip the second file locally,
commit *that* to master with all the changes, make a tag of *that,
etc., etc. in order to have tags with the relevant changes viewable.
It would make the release changes much more accessible.

There's also no technical reason you can't make a top level "tarballs"
directory, similar to branches and tags, and put your archive tarballs
there. It's not standard, but the flexibility is there.

Also, remember that Subversion has no reasonable "obliterate" option,
If you decide later that you don't really want bulky zip files, it's
very awkward to clear them from a source directory. If that source
directory is well defined and not part of the normal expected workflow
directories such as "trunk", "branches", and "tags", it will be safer
and easier to manage later.
Received on 2015-10-18 10:40:37 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.