[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: "Minimized" JavaScript in upstream tarball

INAL, but here's my view:

On Thu, Apr 26, 2012 at 2:34 PM, Dmitry Nezhevenko <dion@inhex.net> wrote:
> Hi,
> I'm trying to package a "web" application that contains some
> minimized third-party JavaScript code. It's from JQuery world.
> Anyway I'm going to package "git" snapshot because latest release needs
> to old versions of dependencies (like django < 1.4).
> So I've a target in debian/rules to get tarball with source snapshot. It
> removes all such JavaScript. Later debian/links creates symlinks to files
> from corresponding libjs-* packages.

Actually, the right thing to do here would be to repack a dfsg free
tarball, and use that to build off of, rather then clean out nonfree
stuff at build-time. This still means anyone who downloads the debian
source is getting some nonfree stuff.

> I've faced an issue where one of JS files is "obfuscated" such way, but
> it's not so populate so it's not in debian now:
> https://github.com/reviewboard/reviewboard/blob/4be2b88fa584d2c958871fce7f9ce20f80b3d7ad/reviewboard/static/rb/js/jquery.masonry.js
> Upstream distributes in both "source" and "minimized" forms:
> http://masonry.desandro.com/jquery.masonry.min.js
> https://github.com/desandro/masonry/blob/master/jquery.masonry.js
> How this particular file should be handled? The only idea I've is to
> remove this file in my get-git-snapshot-source step and download "right"
> one instead.

This should be packaged and pushed to Debian and added as a
dependency, just like anything else :)

It'll make it easier for someone else to use that work as well.

-EPARSE, I might have missed your question due to misreading it, but
that's the best shot at an answer I can rustle up.

> --
> WBR, Dmitry


All programmers are playwrights, and all computers are lousy actors.

#define sizeof(x) rand()

Reply to: