Not really. Just use the information from the grunt config to build the single file javascript using cat. It's a sub-optimal solution because it's a lot of work for doing something upstream allready did, and we can't run the tests. It was actually quite easy with jQuery, working with angular and angular-translate now. Please read the first post of this thread [1], work is allready underway on packaging Grunt, but there are some dependency issues and som (hopefully solved by now) licensing issues.
[1]: https://lists.debian.org/debian-devel/2015/04/msg00056.html -- Andreas Noteng > Den 17. apr. 2015 kl. 01.32 skrev Ian Jackson > <ijack...@chiark.greenend.org.uk>: > > Andreas Noteng writes ("Re: Minified javascripts in packages"): >> Guess I'll have to start over again and figure out how to manually >> concatenate the separate upstream files into one huge file. I can see >> how it makes sense, but it also seems like a lot of work for very >> little gain… > > So you propose to manually reimplement the needed build-time > functionality, for which upstream expect to use grunt ? > > Wouldn't it be easier to package grunt ? Forgive me if I've missed, > in this thread, the explanation of why that's difficult. > > Ian. > > > -- > 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/21808.18062.611515.955...@chiark.greenend.org.uk > -- 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/2df0db4a-0741-4586-94df-c294af3e3...@noteng.no
