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

Re: Release files for setup projects

From: Andreas Schweigstill <andreas_at_schweigstill.de>
Date: Tue, 09 Sep 2008 09:11:18 +0200


Geert van Horrik schrieb:
> Where do you store the release files of a specific tag? For example, you
> have developed 3 versions:

For some projects I have created the following structure:

    |- trunk
    |- tags
    |- branches
    |- releases
         |- version1
             |- sources
             |- binaries
         |- version2
             |- sources
             |- binaries

I found it quite usefull to distinguish between the tags and releases
directories because the latter has a similar but not identical structure
due to the extra directories "sources" and "binaries".

When I create a new release version, I do the following
svn mkdir --parents \
svn cp svn://myserver/projects/my_project/trunk \

svn co svn://myserver/projects/my_project/releases/version3 workdir
cd workdir/sources
nohup make ......
sh cp_files.sh # copy files to binaries directory
cd ../binaries
svn add *
svn ci

After compilation of the project in the sources subdirectory I use
a shellscript which copies all relevant generated files to the
binaries directory in order not to miss some files. For some
projects I also have to do another manual step on some of the
files in binaries which can not be automated.

With best regards
Andreas Schweigstill

Dipl.-Phys. Andreas Schweigstill
Schweigstill IT | Embedded Systems
Schauenburgerstraße 116, D-24118 Kiel, Germany
Phone: (+49) 431 5606-435, Fax: (+49) 431 5606-436
Mobile: (+49) 171 6921973, Web: http://www.schweigstill.de/
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-09-09 09:11:42 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.