Re: Putting the tag name in the tagged code
From: Bryant Eastham <beastham_at_pewla.us.pewg.panasonic.com>
Date: 2007-03-06 22:00:34 CET
Jason-
I guess I am still confused on this issue. I completely agree with
Without starting yet another discussion about product revisions vs.
1. In each deliverable directory we have a "version" file (version
2. Our build targets look for a file build_info (unversioned), and if it
3. If build_info doesn't exist, it is created. If svn is available
4. Source distributions ship build_info as it was created during
All of this allows us to move from trunk to branch, fix problems, go to
We are doing exactly what you mention - shipping libraries to
The trick is making sure that whenever you don't have a WD that your
If you are not willing even to require that level of process, then I
-- Bryant Eastham beastham@pewla.us.pewg.panasonic.com Chief Architect Panasonic Electric Works Laboratory of America, Inc. , Salt Lake City Lab 4525 South Wasatch Blvd., Suite 100, Salt Lake City, Utah 84124 Phone : 801.993.7124 Fax: 801.993.7260 MEW Intranet: https://pewla.mew.com/index.php/User:Beastham -----Original Message----- From: jason marshall [mailto:jdmarshall@gmail.com] Sent: Tuesday, March 06, 2007 11:08 AM To: Bob Hiestand Cc: users@subversion.tigris.org Subject: Re: Putting the tag name in the tagged code Humans transpose numbers. Or forget which tag they were given. The only thing worse than no data is bad data. I'd rather have something called 'foo.jar' that was build 1.23 than have something called foo-1.32.jar that's actually build 1.23. At least I know up front that I have some digging to do. -Jason On 3/6/07, Bob Hiestand <bob.hiestand@gmail.com> wrote: > On 3/5/07, jason marshall <jdmarshall@gmail.com> wrote: > > > > When you run your build process, or use a task in your process to > > > extract the tree, you obviously know which branch/tag you're building. > > > Why not generate an unversioned file in your sandbox at that point > > > and use it during builds? > > > Because I don't 'obviously' know that information. If it's a working > > directory, I could pull it out of the .svn information, sure. But if > > it's a source distribution, or if I can't rely on svn, then it's a > > manual process, and the whole point of the exercise is to take the > > human out of the loop. > > A human somewhere makes a choice when extracting the source from SVN > or any source control system to specify the tag. The build systems > with which I currently work (CVS-based, incidentally) are given a tag > as input, and extract, build, and package the resulting components. > Included in that activity is recording the given tag where it is > desired. > > In any event, it sounds like you're covered. > > Thank you, > > Bob > -- - Jason --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org For additional commands, e-mail: users-help@subversion.tigris.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org For additional commands, e-mail: users-help@subversion.tigris.orgReceived on Tue Mar 6 22:01:03 2007 |
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.