On 2014-08-02 15:00:46 +0800 (+0800), Thomas Goirand wrote: [...] > seeing how it seems to work, it's looking like having the xstatic > packages is the only way so that Horizon knows where to search for > the .js files. [...]
After talking with David Lyle a bit in #openstack-horizon yesterday, I agree. It seems that xstatic provides some standardized glue to tell Django where to find JS libraries, so this probably is the sanest way to integrate them even distro-side. In the case of JS libs which are heavily co-mingled with other software upstream, probably the cleanest solution is to convince the authors to separate those libs out and distribute them isolated from the larger bundle... otherwise you're looking at either forking your own stripped-down source package, or carrying lots of dead code in the source package which won't end up in the binary package (and the latter could lead to conflicts in the future when someone else comes along who actually wants to package the software which is shipping with that library). Anyway, apologies for the detour and thanks for the ongoing packaging effort--that hard work doesn't go unnoticed! -- Jeremy Stanley -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140802134913.gl1...@yuggoth.org