Re: cvs commit: apr-dist/tools release.sh

2003-11-17 Thread Aaron Bannert
On Sat, Nov 15, 2003 at 03:58:55PM -0800, Sander Striker wrote: > > If the RELEASE_VERSION is an optional parameter (in which case the > > script would try to figure out the name of the tarball based on the > > TAG) what happens when the TAG does not contain a version? Does it > > fail? Want to wri

Re: cvs commit: apr-dist/tools release.sh

2003-11-17 Thread Sander Striker
On Sun, 2003-11-16 at 15:51, Aaron Bannert wrote: > On Sun, Nov 16, 2003 at 03:19:42PM -0800, Justin Erenkrantz wrote: > > --On Sunday, November 16, 2003 8:37 PM + [EMAIL PROTECTED] wrote: > > > > >aaron 2003/11/16 12:37:07 > > > > > > Modified:toolsrelease.sh > > > Log: > > >

Re: cvs commit: apr-dist/tools release.sh

2003-11-16 Thread Aaron Bannert
On Sun, Nov 16, 2003 at 03:19:42PM -0800, Justin Erenkrantz wrote: > --On Sunday, November 16, 2003 8:37 PM + [EMAIL PROTECTED] wrote: > > >aaron 2003/11/16 12:37:07 > > > > Modified:toolsrelease.sh > > Log: > > It now takes a CVS TAG *and* a RELEASE_VERSION. > >The TAG is

Re: cvs commit: apr-dist/tools release.sh

2003-11-16 Thread Justin Erenkrantz
--On Sunday, November 16, 2003 8:37 PM + [EMAIL PROTECTED] wrote: aaron 2003/11/16 12:37:07 Modified:toolsrelease.sh Log: It now takes a CVS TAG *and* a RELEASE_VERSION. The TAG is what we pull from CVS. The RELEASE_VERSION is what we call the tarball. As I said in p

Re: cvs commit: apr-dist/tools release.sh

2002-08-28 Thread Greg Stein
This is an initial whack at a release script. It seems to do the job, and produce the right bits. I gotta run right now, but will test it further tonite, then start the release process (mostly, more docs to put into the apr-dist module). If people would like to give this a run, then you can test i