While I'm sure this has been discussed in the past, and upstream
probably has opinions on the topic, the fact is that the WordPress
package in testing now bundles jQuery 3.6.0, while the libjs-jquery
package in testing as of writing provides 3.6.1. As such, I can't
really think of any (technical) reason to continue bundling jQuery
in
the WordPress package rather than depending on libjs-jquery and
symlinking, as is already done for libjs-cropper and
libjs-underscore, and as plenty of other packages already do. This
too could (should?) be a versioned dependency, with a minimum
version.
WordPress bundled jquery has no conflict appended to it. The
linktrees file in the WordPress package source package mentions this:
[..]
Aha, thanks for untangling this for me. I made the (false) assumption
that this was likely a versioning issue; it hadn't occurred to me that
WordPress might be altering jQuery for their bundled copy, though it
also seemed strange that this could have simply been missed in such a
high-profile package. As always, things are more complicated than they
may first appear.
Feel free to close this (or set as duplicate of #591799), unless you
feel particularly inclined to go stir the pot again with upstream.
--
Christer Mjellem Strand
System Administrator
