Joe Orton <joe@manyfish.co.uk> writes:
> That should never be necessary from a release tarball. It looks like
> the generated apr-util/build/rules.mk is included in the 1.0.1 tarball,
> which might be the problem.
>
> $ grep -r kfogel apr-util/
> apr-util/build/rules.mk:apr_builddir=/home/kfogel/src/1.0.x/apr
> apr-util/build/rules.mk:apr_builders=/home/kfogel/src/1.0.x/apr/build
I think the procedures in releases.txt are going to need some
rethinking. Step 5(b) says
b) Run './autogen.sh && ./configure' so the design docs can get
built in the branch tree (in step 4, dist.sh will move the built
design docs into the release sandbox).
The problem with this is that it configures the apr/ and apr-util/
that are about to be copied into the distribution. Someone even
pointed out this problem to me around the time of the release -- was
it CMike? Can't remember, but anyway, I shrugged it off at the
time, saying "Well, we've used these procedures for all previous
releases and they seem to work." Seems I was wrong, at least in
thinking that it was harmless.
It would be much cleaner if, instead of requiring that apr/ and
apr-util/ reside in the working copy tree, dist.sh simply had their
locations passed as explicit arguments:
$ ./dist.sh --apr=/path/to/apr --apr-util=/path/to/apr-util
dist.sh would copy them into the dist while also making sure they
aren't pre-configured.
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Mar 16 19:10:42 2004