Quoting "anatoly techtonik" <techto...@gmail.com>:
There are more than 200 plugins tagged for 0.11 on http://trac-hacks.org/ They were developed and debugged with jQuery 1.2.x which is not forward compatible with 1.3.x
Most Trac plugins do not use JavaScript, even less use jQuery.
I don't feel like I want to check if they are compatible next time I'd like to use one. 15kBytes doesn't worth wasted hours.
The issue is not 15 kB, but the problems Debian would have if an error must be fixed in jQuery (e.g. a security problem). Currently, around 58 packages depend on jQuery. In theory, each of them must have their own copy. Trac does not even depend on jQuery, but only recommends it, because Trac itself does not need jQuery.
The best solution would be to remove "15_remove_jquery_file.dpatch", "postinst", "prerm" and let Trac developers ship the version that contributes to the official API for Trac extension developers for a given Trac release.
If it is really important to have jQuery 1.2 around, the best way would be to ask for a libjs-jquery-1.2 package and let Trac recommend this package instead of libjs-jquery. Anatoly, please file an ITP or RFP bug against the WNPP[1] pseudo-package about libjs-jquery-1.2, OK? Set the maintainer of libjs-jquery in Cc, maybe they will package 1.2 as well. I will change the dependencies in Trac etc. as soon as the package is in. [1] http://www.debian.org/devel/wnpp/ -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org