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

RE: Tags w/build results

From: GOVAERTS Lieven <Lieven.GOVAERTS_at_post.be>
Date: 2005-06-29 14:39:27 CEST

Since branching and tagging are cheap operations in SVN ( meaning, no
Files are duplicated in the repository ), a common use would be:

Develop on trunk.

When code is ready to be released, branch the trunk ( eg. to release 1.x

Checkout your branch ( or switch to your branch ), and add the build

When the branch is complete ( source + build results ), tag it (

If you don't need to make patches on a certain branch, you can disable
access to it
Or finally delete it again.

The only practical difference for you is using a branch instead of a
tag, you
avoid the error message and it gives you the warm feeling using SVN like
should be used :) But again, tagging and branching are cheap operations,
so there
Is no disadvantage using this approach.



-----Original Message-----
From: Andy Peters [mailto:devel@latke.net]
Sent: woensdag 29 juni 2005 3:33
To: users@subversion.tigris.org
Subject: Tags w/build results

I have a quick, probably philosophical, question here.

I'm a hardware guy doing mostly FPGAs in VHDL. For development, I just
keep the sources and scripts in svn on the trunk (unless branched for an
experiment or whatever). Because FPGA place-and-route isn't guaranteed
to be the same every time, we like to include the resulting PROM load
files with the sources that we hand over to production. It would be
convenient to check these results files into the repository. It seems
to me the right way to do this would be to use a tag.

Here's how I do this. I copy the build results (a .mcs or .jed or .bit
file) to a temporary directory. I make sure the WC is updated, then I
tag it. I then switch the WC to the tag, copy the results back to where
they were, add them, then commit them. TortoiseSVN then displays a
helpful warning, "It seems like you're committing to a tag...shouldn't
you be doing this to a branch or the trunk?" but it allows the commit.

Now that the tag has been created, I delete the WC and check out the
trunk if I want to continue working on the design.

Would it be better to simply add the build results to the WC, commit the
change, tag it (leaving the WC still referring to the trunk), then svn
delete the build results?

All thoughts appreciated.

 -- a
Andy Peters devel@latke.net
ASP Digital cell: 520-907-2262
Live Sound Engineering home: 520-791-2716
Digital Circuit Design 5511 E Rosewood St, Tucson, AZ 85711
                                              (note new address!!!)

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

This message may contain confidential and proprietary material for the sole use of the intended recipient. Any review or distribution by others is strictly prohibited. If you are not the intended recipient please contact the sender and delete all copies.

Dit bericht is enkel bestemd voor de aangeduide ontvangers en kan vertrouwelijke informatie bevatten. Als u niet de ontvanger bent, dan mag u de inhoud van dit bericht niet bekendmaken noch kopiëren. Als u dit bericht per vergissing ontvangen heeft, gelieve er de afzender of De Post onmiddellijk van op de hoogte te brengen en het bericht vervolgens te verwijderen.

Ce message est uniquement destiné aux destinataires indiqués et peut contenir des informations confidentielles. Si vous n'êtes pas le destinataire, vous ne devez pas révéler le contenu de ce message ou en prendre copie. Si vous avez reçu ce message par erreur, veuillez en informer l'expéditeur, ou La Poste immédiatement, avant de le supprimer.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jun 29 14:44:10 2005

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.