On Tue, Apr 28, 2015 at 6:37 PM Aaron Bieber <aa...@bolddaemon.com> wrote:
> Hola! > > I hit the tipping point over the weekend. The 0.12.2 update requires an > update to just about every node-* port we have, and each new version > comes with about 3 zillion new dependencies (ok maybe 2 zillion...). > > I have added a new package type to the node.port.mk file called "pkg", > this type lets you rebuild (during port building) a given package for > the arch it is going to be run on. > > The basic procedure for creating these packages is: > > mkdir /tmp/crap; > cd /tmp/crap && npm install <module> > cd <module> > tar -czvf <module>-0.0.0.tgz <module> > *upload to server* > > Now you add your MASTER_SITES to a makefile similar to the one attached > (for node-sqlite3). I will host the tarballs for anyone interested in > doing this. > > Running "make" will pull in the tarball and recursively rebuild all the > submodules (assuming they are native modules). This allows us to avoid > having to import every dep prior to creating a port. It also eliminates > some of the version clobbering that happens when a module depends on a > different version of a given module. > > It isn't exactly clean yet, and I would appreciate any clue sticks. I am > also holding my breath for a better solution from GSoC! > > I have only tested node-sqlite3 on amd64 and i386. The plist needed a > bit of manual cleanup as some home directory cruft gets added by npm. > Builds just fine with your updates. I've been using it for a while now and the nagging issues I have about node running off into the weeds and destroying my machine are gone. I was able to run a dev instances for several days without issue. This was impossible before. From my standpoint the node update looks fine. I cannot really speak about all the dependencies. Brandon
