You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Andy Peters <de...@latke.net> on 2005/06/29 01:33:15 UTC
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
Re: Tags w/build results
Posted by Andy Peters <de...@latke.net>.
kfogel@collab.net wrote:
> "Andy Peters" <de...@latke.net> writes:
>
>> 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.
>> 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/
> ...
> ...
> prom_load_file
> ...
> ...
> $
Ahhhh, yes, I like that!
Thanks!
-a
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Tags w/build results
Posted by kf...@collab.net.
"Andy Peters" <de...@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/
...
...
prom_load_file
...
...
$
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Tags w/build results
Posted by Marcus Rohrmoser <mr...@gmx-gmbh.de>.
What about a 2nd repo for deliverables (build output e.g.) only? Every
tag in the src repo could correspond to a commit to the bin repo.
Greetings,
M
Andy Peters schrieb:
> 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
>