[Bug 204577] [NEW MODULE] Mk/Uses/nodejs.mk Framework for NodeJS projects/ports

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204577

--- Comment #31 from Torsten Zühlsdorff <ports at toco-domains.de> ---
(In reply to yuri from comment #27)

> There are hundreds of modules, and they can be, and are present in different 
> versions within the same process. This is the major feature of NodeJS that it 
> 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. But
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 fetching
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 clear
how do you solve it. Can you please explain this to me?

-- 
You are receiving this mail because:
You are on the CC list for the bug.