On Mon, Aug 17, 2015 at 10:38 PM, Aaron Bieber <[email protected]> wrote: > > Alexey Suslikov writes: > >> On Mon, Aug 17, 2015 at 9:29 PM, Aaron Bieber <[email protected]> wrote: >>> >>> Alexey Suslikov writes: >>> >>>> Aaron Bieber <aaron <at> bolddaemon.com> writes: >>>> >>>>> I am also looking for suggestions on how to move forward with this.. As >>>>> I see it we have two options.. 1) keep waiting until I sort out the issues >>>>> with npm.. and keep everything at an older version for now.. or 2) update >>>>> node to 0.12.7 and mark the current node-* ports as broken (maybe even >>>>> remove them?). >>>> >>>> We discussed this previously: how about modules with native lib >>>> binding? >>>> >>> >>> The new "pkg" type (see the diff for node.port.mk) supports native >>> modules. Basically every thing is built as a self contained tarball, >>> then the native stuff is rebuilt during build. >>> >>> I have attached an example of how the databases/sqlite3 (a native >>> module) port would be updated. >> >> I remember you did post an example how to build such a "pkg". >> >> Could you please point to this example or re-post it so I can try >> to adapt (long stalled) updates to new scheme? >> > > Executing the previously attached "mk_npm_dist" script creates a .tar.gz > of a given npm package that can be used as a distfile for a port. > > Example usage: > ./mk_npm_dist sqlite3 > ...lots of output... > Created: /tmp/tmp.74ehtPh8Ur/sqlite3-3.0.10.tar.gz > > Upload the sqlite3 tarball and add the new location to MASTER_SITES in > the makefile, then change CONFIGURE_STYLE to be "npm pkg", regen your > PLIST and you should be good to go! (except for the path thing I > mentioned earlier :P)
Thanks. On deleting packages. Can port quirks help with proper upgrade path? For instance, node-pg being a dual package (native js and native binding), now is the couple of packages: one for native js, one for native binding. If node-pg port will be upgraded, upgrade path should be to replace what we currently have (dual) with native binding port only (because there is no point to package native js version). My 2 cents.
