[Mulgara-dev] Re: build issues
Life is hard, and then you die
ronald at innovation.ch
Tue Jul 17 21:34:33 UTC 2007
Aarg! My screwup. Sorry. Everybody has the command line subversion on
all the other projects I work on, so this never occurred to me.
On Tue, Jul 17, 2007 at 03:47:40PM -0500, Paul Gearon wrote:
> It takes the latest checkout version (around 320 at the moment) and
> uses that in the revision number. So you get a build of 1.1.0-r320,
> or something like that.
>
> This way, you can differentiate between different builds out of
> subversion. But not being able to build without subversion is a big
> deal. It really needs to ignore this if you don't have .svn in your
> current directory!
Will that help? Don't TortoiseSVN, RapidSVN etc use the same .svn
files?
I see two solutions: trying to figure out what subversion client is
installed and try to use that to get the svn-version, or just sticking
a dummy string in there if 'svnversion' isn't available. Actually, we
probably need both approaches.
David, does TortoiseSVN have the equivalent of svnversion and can it
be run as a command-line tool?
Cheers,
Ronald
> On 7/17/07, David Moll <DMoll at myaperio.com> wrote:
> >
> >>I'll hassle the guy who wrote this patch to come up with a solution.
> >>Are you OK with it for a couple of days?
> >>
> >>Paul
> >
> >Absolutely. I'm running build-test now and everything seems fine. What
> >is the subversion section in the build script going to do? I'm curious
> >and can't really decipher ant xml files yet.
> >
> >Also, I imagine that there could be a fallback to check for TortoiseSVN
> >if Subversion isn't found.
> >
> >Thanks for the assistance with this Paul.
> >
> >~Dave
> >
> _______________________________________________
> Mulgara-dev mailing list
> Mulgara-dev at mulgara.org
> http://mulgara.org/mailman/listinfo/mulgara-dev
More information about the Mulgara-dev
mailing list