Bruno Haible <[email protected]> writes: > Exactly, that's the point. Does he do it like this always, and what if he > forgets it once? That is, if in one of his poke checkouts he runs > > ./autopull.sh --jitter-srcdir="$HOME/gnu/jitter-experimental" > ./autogen.sh > > Will he get a mix of derived files from $HOME/gnu/jitter-experimental > and ./jitter (with likely breakage)? > > Or is the directory name $HOME/gnu/jitter-experimental being remembered > somewhere, making it unnecessary to repeat it?
He'd get whatever Jitter poke declares as a submodule, no remembering
anything. The behavior for GNULIB_SRCDIR appears to be just skipping
the checkout instead.
Out of curiosity, I tried building after an
./autogen.sh --jitter-srcdir="$HOME/gnu/jitter-experimental"
call, and it'd appear to fail for other reasons currently:
=== configuring in jitter (/tmp/poke/jitter)
configure: WARNING: no configuration information is in jitter
configure: back from the recursive configuration in jitter
checking for jitter-config... no
configure: can't find jitter-config
configure: error: could not find jitter-config in Jitter sub-package within
jitter
... but by changing the JITTER_JITTER_SUBPACKAGE invocation to check the
JITTER_SRCDIR variable, configure finishes, but make fails because
jitter is declared in SUBDIRS as just "jitter".
This use-case might take a bit more work to figure out. I can do that
too given some time to think (so far, I'm leaning towards only having
JITTER_REFDIR that behaves as GNULIB_REFDIR does).
WDYT?
Thanks in advance.
--
Arsen Arsenović
signature.asc
Description: PGP signature
