* Paul Tagliamonte <paul...@debian.org>, 2014-03-18, 09:13:
That would work only if the embedded copy was the same version as the
packaged one. And there are lots of jQuery versions in the wild.
In <20120817111437.ga8...@jwilk.net> I suggested making a package that
would bundle all the needed sources, but my proposal wasn't met with
enthusiasm.
I think this mega-package might actually be hella useful, but I think
it'd be useful if we do some dh-foo to automagically strip and link
copies at build-time, so that we *never* ship a jquery file (if it's a
matching shasum or something), but it strips it and turns it into a dep
+ symlink.
Just to be clear, for the moment I'm advocating only a source
mega-package, which should be dead easy to implement.
Binary mega-package is a more ambitious task, especially if you intend
that other users will use it.
As for having the source to a source package in another source package?
Hurm. I don't know how I feel about that, but I don't think I like it.
Hey, I don't like it either. But I dislike status quo even more.
Stuffing the source to a separate package is better than stuffing it to
.diff.tar (or diff.gz), and the latter is already happening.
If binary packages are allowed to have source in foreign source
packages, why wouldn't source packages be allowed to do the same?
--
Jakub Wilk
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140318190706.gb7...@jwilk.net
