On Fri, 17 Oct 2014, Aaron Bieber wrote: > I thought I was losing my mind.. couldn't figure out why we never > noticed this before. > > If we can't trick npm into thinking it has the modules already installed > it tries to grab them from the npmjs registry. > > Apparently we never noticed it because node.js shipped with version > 0.3.5 of mkdirp and we were able to symlink it into the coffeescript > stuff. > > Making a package of it now results in a collision with the nodejs > package.. Sigh.
What about the diff below? On github I didn't see significant differences between mkdirp 0.3.5 and mkdirp 0.5.0, so it should work without problems. Index: Makefile =================================================================== RCS file: /cvs/ports/lang/coffeescript/Makefile,v retrieving revision 1.17 diff -u -p -u -p -r1.17 Makefile --- Makefile 31 Aug 2014 10:48:53 -0000 1.17 +++ Makefile 18 Oct 2014 18:56:31 -0000 @@ -7,6 +7,7 @@ COMMENT = little language that compiles NPM_VERSION = 1.8.0 NPM_NAME = coffee-script PKGNAME = coffeescript-${NPM_VERSION} +REVISION = 0 CATEGORIES = lang MAINTAINER = Jasper Lievisse Adriaanse <jas...@openbsd.org> Index: patches/patch-package_json =================================================================== RCS file: patches/patch-package_json diff -N patches/patch-package_json --- /dev/null 1 Jan 1970 00:00:00 -0000 +++ patches/patch-package_json 18 Oct 2014 18:56:31 -0000 @@ -0,0 +1,11 @@ +$OpenBSD$ +--- package.json.orig Sat Oct 18 20:28:19 2014 ++++ package.json Sat Oct 18 20:28:38 2014 +@@ -39,6 +39,6 @@ + "docco": "~0.6.2" + }, + "dependencies": { +- "mkdirp": "~0.3.5" ++ "mkdirp": ">=0.3.5" + } + }