| Re: Coyote Library Updates [message #77204 is a reply to message #62777] |
Tue, 09 August 2011 10:27   |
David Fanning
Messages: 11724
Registered: August 2001
|
Senior Member |
|
|
Paul van Delst writes:
> Are you planning on creating svn tags of these releases? And, with apologies for the preaching, but how come you don't
> create the zip files from said tagged release? That should avoid wrong files being copied.
I've experimented (because of your nagging!) with
tagged releases. It's probably because I don't fully
understand what I am doing, but I don't like tagged
releases. Mostly because two minutes after I tag
a release someone reports a bug, and then the tagged
release is obsolete and SVN seems to not allow me to
change it. I am embarrassed to create a NEW tagged
release two minutes after the old one. It makes it
seem (duh!) like I don't know what I am doing!
> Additionally, that would allow outside users of your package to update their own source code histories with the tag name
> of your release. Or, in my case, export your tagged release into my own repo -- I'm not allowed to use svn:externals :o(
>
> Traceability and all that, you know?
OK, here is how I work. I have two folders, Coyote and Zip_Files, under
my IDL directory. When I make a change to a file that I think is a
"significant" change (meaning, in practice, any change at all,
because I am so damn anal!) I add the change to the coyoteprograms.zip
file and I commit both the zip file and the program files to the Goggle
SVN repository. Then, I "update" the same two folders that exist
in my copy of my web page on my computer. After the update, I
copy the updated files from my local web page to my real web page.
I update Coyote Library routines frequently, probably at least once
a week, and occasionally (when I'm not completely on my game)
several times a day. The SVN repository includes the latest
files. My web page contains the latest files. I would think that
would be enough, but...
What exactly do you want me to do? I'm interested in doing
whatever works for people. Tell me how you would use these
tagged releases, given what you know about my complete
inability to serve up files that I know are out of date.
Is it permissible to create tagged releases several times
a day, or would I run out of release numbers. :-)
And, how would these tagged releases be any different from
the files that are already in the SVN repository? I mean, isn't
this just extra work?
Cheers,
David
--
David Fanning, Ph.D.
Fanning Software Consulting, Inc.
Coyote's Guide to IDL Programming: http://www.idlcoyote.com/
Sepore ma de ni thui. ("Perhaps thou speakest truth.")
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
