[Octave-bug-tracker] [bug #57044] Use gnulib without hg subrepo and `bootstrap` with proper revision control

[Kai Torben Ohlhus]

Follow-up Comment #12, bug #57044 (project octave):

Indeed, bootstrap is a very "intelligent" script, that can ensure using the
correct "GNULIB_REVISION" all by its own.

Regarding older releases, soon 5.2.0 and older:  There the files ".hgsub" and
".hgsubstate" are still present in the repository and will have to use
Octave's gnulib hg subrepo https://hg.octave.org/gnulib/ to work in the
future.  Thus we cannot delete Octave's gnulib hg subrepo, if we want to be
able to know the gnulib version of that releases.

Regarding releases 6.1 and onwards: ".hgsub" and ".hgsubstate" are removed. 
The "GNULIB_REVISION" is maintained in "bootstrap.conf" inside Octave's main
hg repository.  Thus it is clear for every commit, which "GNULIB_REVISION" was
in use.  The hard work is done by bootstrap itself.

Scenario #1: In a fresh Octave hg repo.  Just calling


./bootstrap


will check for "./gnulib/" to be a clone of git://git.sv.gnu.org/gnulib
(https://git.savannah.gnu.org/cgit/gnulib.git) and clone it if not existing. 
If existing, bootstrap tries to checkout "GNULIB_REVISION".  This works, even
if the "GNULIB_REVISION" is in the future, i.e. not fetched inside
"./gnulib/".

Scenario #2: In a fresh Octave hg repo.  Custom gnulib git repo


./bootstrap --gnulib-srcdir=path/to/gnulib


and the procedure is as in #1.

As said before in comment #10.  Updating gnulib from 6.1 will be pretty easy
compared to now.  Never had such a close look at bootstrap before.


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?57044>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/