Date: Sun, 06 Dec 2015 16:49:50 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 204577] [NEW MODULE] Mk/Uses/nodejs.mk Framework for NodeJS projects/ports Message-ID: <bug-204577-13-erCwDA16Fi@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-204577-13@https.bugs.freebsd.org/bugzilla/> References: <bug-204577-13@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204577 --- Comment #26 from Olivier Duchateau <olivierd@FreeBSD.org> --- (In reply to yuri from comment #25) I don't understand, why you persist to use Github? If useful module is hosted an another host (and use another revision control system), user must re-define npm-fetch target. I think it's more simple to use the npm registry website, moreover tarballs are well formed and name is generic. So it can be generalized in framework. I do not agree to include node.js submodules. I prefer to have one port per module. IMHO, Grunt and CoffeeScript should be placed in independent files (for example Mk/Uses/grunt.mk and Mk/Uses/coffeescript.mk), loading right variables environment in order to configure and build packages. -- You are receiving this mail because: You are on the CC list for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-204577-13-erCwDA16Fi>