Re: [lmi] [PATCH] Use submodules for, and newer versions of, libxml2 and libxslt

[Greg Chicares]

On 2020-10-01 16:21, Vadim Zeitlin wrote:
> On Thu, 1 Oct 2020 15:33:31 +0000 Greg Chicares <gchicares@sbcglobal.net> 
> wrote:
> 
> GC> Should we upgrade to the latest libxml2 now, just because it's the
> GC> perfect time for that?
[...]
>  So I wanted to write that I'll do it soon, but then I started wondering if
> it could be useful for you to try to do it just to ensure that you can do
> it if necessary? Please let me know if you'd be interested in such an
> exercise (I hope asking you this right now doesn't constitute abuse of
> weakness...).

The latest official release is 41a34e1f:
  https://gitlab.gnome.org/GNOME/libxml2/-/tags/v2.9.10

I did spend some time trying to figure this out. Editing '.gitmodules',
which now has...

[submodule "third_party/libxml2"]
        path = third_party/libxml2
        url = https://github.com/let-me-illustrate/libxml2.git
        branch = lmi

...seemed like an idea worth trying--e.g., speculatively:

-       url = https://github.com/let-me-illustrate/libxml2.git
-       branch = lmi
+       url = https://gitlab.gnome.org/GNOME/libxml2/
-       branch = 41a34e1f
                 ^^^^^^^^ NOT

which would be perfect except that a tag is not a branch. Apparently
there are various ways to deal with this for various versions of git,
but all involve a deep dive into git submodules. But I'm already deep
in git-merge, and attempting to dive deeply into more than one git
topic at once is not a good idea while I have other work to do.
Therefore...

>  In this particular case, I think we should just upgrade libxml2, which
> will fix this issue as a side effect.
> 
>  Just please let me know if we should do it or if you will,

...yes, please do update libxml2.