Date: Mon, 14 Dec 2015 16:10:20 +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-hpFlbCU0av@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=3D204577 --- Comment #31 from Torsten Z=C3=BChlsdorff <ports@toco-domains.de> --- (In reply to yuri from comment #27) > There are hundreds of modules, and they can be, and are present in differ= ent=20 > versions within the same process. This is the major feature of NodeJS tha= t it=20 > supports this. And it is a major disadvantage. I discovered multiple projects which could = not build anymore, because the old versions were no longer provided! We have 2 different approaches here and 2 persons which do much work to get their way working. That is great! Thank you both for your efforts! But i think we should discuss the advantages and disadvantages of both solutions and try to find the way we want. >From my point of view: There are many different modules and it is a major task to make single ports for them. This is an error prone but working way, as rubygems teached us. B= ut this as the advantage that everything is clear and known Creating bundles saves as the port managing, which is a huge advantage. But= we need a way to guarantee that everything is know before installing (no fetch= ing of new libs after fetch-phase). Also how to you handle multiple usage of the same library? Multiple installation, references, etc? Currently it is not c= lear how do you solve it. Can you please explain this to me? --=20 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-hpFlbCU0av>