[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: <kfogel_at_collab.net>
Date: 2005-06-29 04:56:12 CEST

"Andy Peters" <devel@latke.net> writes:
> 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

Why not just do this instead?

   $ cd your_regular_trunk_working_copy
   $ cp ../../../wherever/prom_load_file .
   $ svn add prom_load_file
   $ svn cp -m "Create Release 2.3 tag." . http://.../repos/tags/release-2.3
   $ svn revert prom_load_flie
   $ rm prom_load_file
   $ svn ls http://.../repos/tags/release-2.3/


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jun 29 05:43:46 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.