packages depending from libxml2_2

marco atzeri marco.atzeri@gmail.com
Sun Nov 8 17:42:16 GMT 2026


On Sat, 7 Nov 2026, 15:35 Jon Turney via Cygwin-apps, <
cygwin-apps@cygwin.com> wrote:

> On 06/11/2026 10:57, Jon Turney via Cygwin-apps wrote:
> > On 06/11/2026 10:35, Marco Atzeri via Cygwin-apps wrote:
> >> On 05/11/2026 19:42, Jon Turney via Cygwin-apps wrote:
> >>> On 04/11/2026 16:39, Marco Atzeri via Cygwin-apps wrote:
> >>>> Hi Jon,
> >>>>
> >>>> just uploaded libxml2_2-2.13.9-3
> >>>>
> >>>> I will wait few days before uploading 2.15.4-2
> >>>>
> >>>> $ find . -name "*.xz"
> >>>> ./libxml2/libxml2-2.15.4-2-src.tar.xz
> >>>> ./libxml2/libxml2-2.15.4-2-x86_64.tar.xz
> >>>> ./libxml2/libxml2-debuginfo/libxml2-debuginfo-2.15.4-2-x86_64.tar.xz
> >>>> ./libxml2/libxml2-devel/libxml2-devel-2.15.4-2-x86_64.tar.xz
> >>>> ./libxml2/libxml2-doc/libxml2-doc-2.15.4-2-x86_64.tar.xz
> >>>> ./libxml2/libxml2_16/libxml2_16-2.15.4-2-x86_64.tar.xz
> >>>> ./libxml2/python312-libxml2/python312-libxml2-2.15.4-2-x86_64.tar.xz
> >>>> ./libxml2/python39-libxml2/python39-libxml2-2.15.4-2-x86_64.tar.xz
> >>>>
> >>>> probably the best way to handle is for every package that requires
> >>>> libxml2 to add libxml2_2 dependency
> >>>
> >>> Just so I'm understanding correctly: libxml2 and libxml2_2 both
> >>> provide cygxml2-2.dll?
> >>
> >> Hi Jon,
> >>
> >> until 2.13.9-2 libxml2
> >> contained both the utilities and the dll
> >>
> >> /usr/bin/xmlcatalog.exe
> >> /usr/bin/xmllint.exe
> >> /usr/bin/cygxml2-2.dll
> >>
> >> now from 2.13.9-3 they are split
> >>
> >> $ cygcheck -l libxml2 |grep bin
> >> /usr/bin/xmlcatalog.exe
> >> /usr/bin/xmllint.exe
> >>
> >> $ cygcheck -l libxml2_2 |grep bin
> >> /usr/bin/cygxml2-2.dll
> >
> > Aha! That makes sense.
> >
> > OK. I see what you are trying to do now.
> >
> >> libxml2 2.13.9-3 now pulls libxml2_2.
> >>
> >> I assume most of the programs requiring libxml2 need only the
> >> cygxml2-2.dll but it is possible that some require also the *.exe
> >> utilities
> >>
> >> from 2.15.4-2 libxml2 will pull libxml2_16
> >
> > Hmm...  It would be easier to put the executables in a new package
> > called 'libxml-utils' or 'libxml-tools' or similar.
> >
> > Then we won't need to mess with the things that already point to libxml2
> > (which can stay as an alias for libxml2_2 for old packages).
> >
> > (Although there will be, as you mention, some change for anything which
> > wants xmllint).
> >
> >> /usr/bin/cygxml2-16.dll
> >>
> >> after I will upload 2.15.4-2 any package that needs cygxml2-2.dll
> >> will have a missing pull and we will heard complaints from new
> >> installation and from people upgrading after 2.15.4-2 is deployed.
> >>
> >> Easy solution is for the current packages that requires libxml2 to
> >> require also libxml2_2. This will maintain consistency until every of
> >> those package is updated
> >>
> >> Does make sense ?
> >> I would like to avoid that on  2.15.4-2 libxml2 directly pull both
> >> libxml2_16 and libxml2_2
>
> Well, on further consideration, I think I could be persuaded that either
> of these is the right approach.
>
> Let me know which you prefer.
>
> (I already have a tool to adjust the existing dependencies, so it's
> relatively straightforward to do that if that's what you want).
>

Please add libxml2_2 to all requiring libxml2.
In this way there should be no broken package when i deploy 2_16

>


More information about the Cygwin-apps mailing list