You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Jennifer Kesterson <Je...@jpl.nasa.gov> on 2005/10/19 15:01:09 UTC
Building up baseline repository with old builds
Hello,
I hope this hasn't already been asked and answered a million times but I
wouldn't know where to begin to search for this in the archives, so here
goes.........
We're a new project but we've already completed some builds. We didn't
have a formal CM system set up for those builds but we are preparing
Subversion for use before the next build.
We'd like to establish our baseline in the Subversion repository by
importing Build 1.0, then adding 1.1 on top of that, then 2.0, then 2.1,
and tagging each one after it is imported, so that the end result is a
repository that looks as if we had been using it from the beginning.
What is the best way to do this? I'm a relatively new user and from my
limited experience I know that importing Build 1.0 and tagging it will be
easy. From there, how do we import the subsequent builds on top of
that? Is it possible? If not, then I'm wondering if we could import build
1.0, tag it, then import 1.1 into a separate tree and tag it, then do the
same with 2.0 and 2.1, then import the current set of development code into
the main trunk and continue from there.
I'd appreciate your help and guidance with this.
Thanks,
Jen
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Building up baseline repository with old builds
Posted by Jennifer Kesterson <Je...@jpl.nasa.gov>.
>
>It's linked from here:
>
>http://subversion.tigris.org/issues/show_bug.cgi?id=2241
>
Thank you!
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Building up baseline repository with old builds
Posted by Ryan Schmidt <su...@ryandesign.com>.
On Oct 19, 2005, at 22:03, Jennifer Kesterson wrote:
>> Read all about the svn_load_dirs Perl script that's in the contrib
>> directory. It's designed for loading third-party libraries into your
>> Subversion repository, but it works just as well for importing your
>> old builds.
>>
>> The version included with Subversion doesn't handle symlinks, but
>> there is a patch that adds symlink support if you need it, which also
>> worked great for me.
>>
>
> Thank you very much. Where would I find that patch?
>
It's linked from here:
http://subversion.tigris.org/issues/show_bug.cgi?id=2241
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Building up baseline repository with old builds
Posted by Jennifer Kesterson <Je...@jpl.nasa.gov>.
>
>Gmane /prvides some useful searching and archiving utlilties. The page
>for this list is at:
>
>http://dir.gmane.org/gmane.comp.version-control.subversion.user
>
>- hoffer
Thank you, I bookmarked the link.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Building up baseline repository with old builds
Posted by Michael Hordijk <ho...@hotmail.com>.
Jennifer Kesterson wrote:
>> I had to ask too when I need to do this for a project some months
>> ago. :-) It's not the easiest thing to search the archives for.
> I wouldn't know where to begin. :-)
Gmane /prvides some useful searching and archiving utlilties. The page
for this list is at:
http://dir.gmane.org/gmane.comp.version-control.subversion.user
- hoffer
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Building up baseline repository with old builds
Posted by Jennifer Kesterson <Je...@jpl.nasa.gov>.
>
>I had to ask too when I need to do this for a project some months
>ago. :-) It's not the easiest thing to search the archives for.
I wouldn't know where to begin. :-)
>Read all about the svn_load_dirs Perl script that's in the contrib
>directory. It's designed for loading third-party libraries into your
>Subversion repository, but it works just as well for importing your
>old builds.
>
>The version included with Subversion doesn't handle symlinks, but
>there is a patch that adds symlink support if you need it, which also
>worked great for me.
Thank you very much. Where would I find that patch?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Building up baseline repository with old builds
Posted by Ryan Schmidt <su...@ryandesign.com>.
On Oct 19, 2005, at 17:01, Jennifer Kesterson wrote:
> Hello,
> I hope this hasn't already been asked and answered a million times
> but I wouldn't know where to begin to search for this in the
> archives, so here goes.........
>
I had to ask too when I need to do this for a project some months
ago. :-) It's not the easiest thing to search the archives for.
> We're a new project but we've already completed some builds. We
> didn't have a formal CM system set up for those builds but we are
> preparing Subversion for use before the next build.
>
> We'd like to establish our baseline in the Subversion repository by
> importing Build 1.0, then adding 1.1 on top of that, then 2.0, then
> 2.1, and tagging each one after it is imported, so that the end
> result is a repository that looks as if we had been using it from
> the beginning.
>
> What is the best way to do this? I'm a relatively new user and
> from my limited experience I know that importing Build 1.0 and
> tagging it will be easy. From there, how do we import the
> subsequent builds on top of that? Is it possible? If not, then
> I'm wondering if we could import build 1.0, tag it, then import 1.1
> into a separate tree and tag it, then do the same with 2.0 and 2.1,
> then import the current set of development code into the main trunk
> and continue from there.
Read all about the svn_load_dirs Perl script that's in the contrib
directory. It's designed for loading third-party libraries into your
Subversion repository, but it works just as well for importing your
old builds.
The version included with Subversion doesn't handle symlinks, but
there is a patch that adds symlink support if you need it, which also
worked great for me.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Building up baseline repository with old builds
Posted by Jennifer Kesterson <Je...@jpl.nasa.gov>.
>
> >
>Take a look at svn_load_dirs.pl.
>http://svn.collab.net/repos/svn/trunk/contrib/client-side/svn_load_dirs.README
>
>Josh
Thank you!
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Building up baseline repository with old builds
Posted by Jennifer Kesterson <Je...@jpl.nasa.gov>.
>
>You have to make sure that you unpack each build into a separate
>directory. For example, if you have two archives cookie-1.0.tar.gz
>and cookie-1.1.tar.gz, and both unpack into a directory 'cookie/',
>you will have to do something like this:
>
> tar xvfz cookie-1.0.tar.gz; mv cookie cookie-1.0
> tar xvfz cookie-1.1.tar.gz; mv cookie cookie-1.1
>
>With this, you can now use the script on the directories in parallel.
>
>Alternatively (I haven't tried this, but it might work), unpack and
>import each build in sequence:
>
> tar xvfz cookie-1.0.tar.gz
> svn_load_dirs.pl -t tags/1.0 URL cookie
> rm -r cookie
>
> tar xvfz cookie-1.1.tar.gz
> svn_load_dirs.pl -t tags/1.1 URL cookie
> rm -r cookie
>
>Cheers,
> Lars
>--
Thanks so much, that makes more sense. I guess I should learn to read
between the lines! <:-|
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Building up baseline repository with old builds
Posted by Lars Duening <la...@bearnip.com>.
On Oct 19, 2005, at 6:45 PM, Jennifer Kesterson wrote:
>> Take a look at svn_load_dirs.pl.
>> http://svn.collab.net/repos/svn/trunk/contrib/client-side/
>> svn_load_dirs.README
>>
>
> I read through the README file and I understand most of it but I
> have a question:
>
> In Step 1 (of README) it says to untar the tar files into a
> directory. But if I untar all the tar files into the same
> directory, files will be overwritten by newer files of the same
> name in subsequent deliveries (tar files). Is this step assuming
> multiple versions of the same file don't exist in more than one tar
> file? What I'm left with is only one version of each file.
You have to make sure that you unpack each build into a separate
directory. For example, if you have two archives cookie-1.0.tar.gz
and cookie-1.1.tar.gz, and both unpack into a directory 'cookie/',
you will have to do something like this:
tar xvfz cookie-1.0.tar.gz; mv cookie cookie-1.0
tar xvfz cookie-1.1.tar.gz; mv cookie cookie-1.1
With this, you can now use the script on the directories in parallel.
Alternatively (I haven't tried this, but it might work), unpack and
import each build in sequence:
tar xvfz cookie-1.0.tar.gz
svn_load_dirs.pl -t tags/1.0 URL cookie
rm -r cookie
tar xvfz cookie-1.1.tar.gz
svn_load_dirs.pl -t tags/1.1 URL cookie
rm -r cookie
Cheers,
Lars
--
Lars Duening; lars@bearnip.com
GPG Key: http://www.bearnip.com/lars/lars-duening.gpgkey
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Building up baseline repository with old builds
Posted by Jennifer Kesterson <Je...@jpl.nasa.gov>.
>
>Take a look at svn_load_dirs.pl.
>http://svn.collab.net/repos/svn/trunk/contrib/client-side/svn_load_dirs.README
I read through the README file and I understand most of it but I have a
question:
In Step 1 (of README) it says to untar the tar files into a directory. But
if I untar all the tar files into the same directory, files will be
overwritten by newer files of the same name in subsequent deliveries (tar
files). Is this step assuming multiple versions of the same file don't
exist in more than one tar file? What I'm left with is only one version of
each file.
The instructions don't seem to suggest that I untar them into separate
directories since the script is run from this directory.
To clarify again, what I want to do is import the source files from build
1.0 and tag it, then import the files from build 1.1 (which contains
updated files from 1.0) and tag it, then import build 2.0 and 2.1 in the
same way -- all into the same directory tree. The desired outcome is to
have every version of <file> imported into the same repository tree and to
be able to recover any version of that file. Is this what the script
actually does?
Thanks,
Jen
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org