Pirate Praveen: > Control: tags -1 -moreinfo > > On Sat, 18 Feb 2017 09:54:00 +0000 Niels Thykier <ni...@thykier.net> wrote: > >> I think the best solution here is to start with a dh-grunt prototype, >> which can evolve in its own pace (notably a lot faster than debhelper >> itself). Once it has matured, we can look at merging it into debhelper >> itself depending on its (build-)dependency requirements. > > May be we can have dh-nodejs. >
Sure; the idea more about you developing the prototype in a separate package and less about the concrete name of the package. We can also do it inside debhelper, but then you get changes at the pace of debhelper releases plus the stability woes/guarantees of debhelper (e.g. at some point it will take compat bumps to fix things). If those are "good enough" for you, then I am fine with going that direction. >> FTR, I know next to nothing about grunt/nodejs builds, so I am a poor >> choice for driving such a prototype. However, I am happy to assist with >> the debhelper integration bit. > > I think it does not need any nodejs knowledge. If you find a > Gruntfile.js or Gruntfile.coffee, just call "grunt build". > > Same for gulp, if you find a Gulpfile.js, just call "gulp build". > > Also for cake, if you find Cakefile, just call "cake.coffeescript build". > I assume that the above instructions cover "dh_auto_build" and "auto-detection". What do I do for: * dh_auto_configure? (Nothing?) * dh_auto_test? (<tool> test | <tool> check?) * dh_auto_install? (<tool> install DESTDIR=.../debian/tmp/ ?) * dh_auto_clean? (<tool> clean?) Should I pass any flags for some tools to (e.g.) disable internet usage, tweak which tests are being run, choose where stuff is installed, whether files are minimized, etc.? Thanks, ~Niels
