On Tue, Mar 28, 2017 at 07:02:37PM +0100, Tom Hughes wrote:
On 28/03/17 18:49, Christopher wrote:
> The current version in Fedora is 2.2.4 (which is quite old now). I don't
> know what it might break... I'm not even sure how to check which
> packages depend on js-jquery. I've only taken over js-jquery because it
> was orphaned for awhile, I need it for my package, and I didn't want it
> to get retired. One thing I know... it's not reasonable to keep
> packaging *every* major version of jQuery. Currently, there is
> js-jquery1 (which is the last version 1) and js-jquery (which is the
> last version 2). I would like to retire js-jquery1 eventually, and just
> keep js-jquery at the latest.
Well rubygem-jquery-rails is a definite issue:
rubygem-jquery-rails-0:4.2.2-2.fc26.noarch
jquery = 1.12.4
jquery = 2.2.4
As far as I can see nothing else has an require that would actually be
broken, and I don't think 2 to 3 is as big an issue as 1 to 2 so you might
be ok.
You need to talk to the rubygem maintainer though, as that always has to be
updated in lockstep with the main package.
python-XStatic-JQuery depends on js-jquery1 (and about 15 other
packages)
For those folks requiring jquery to upgrade to 3, how about introducing
js-jquery2 (for backwards compatibility) and upgrading js-jquery then?
Up to a certain point of time, it was ok to bundle js libs, you'd just
punish those maintainers who unbundled them.
--
Matthias Runge <mrunge(a)redhat.com>