Date: Wed, 17 Mar 2021 15:27:40 -0400 From: Steve Wills <steve@mouf.net> To: Mathieu Arnold <mat@freebsd.org>, Juraj Lutter <otis@freebsd.org> Cc: ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: Re: svn commit: r568508 - head/devel/node-gyp Message-ID: <80fc0f66-44b1-f7d3-fc36-b78d63bc753b@mouf.net> In-Reply-To: <20210316221912.smaeylfqtx7yfm6i@aching.in.mat.cc> References: <202103152102.12FL2tRP068067@repo.freebsd.org> <20210316211715.pa4w3lrffzxr3ftx@aching.in.mat.cc> <2239997E-E3B6-403F-B36D-4326CDF16EFE@FreeBSD.org> <20210316221912.smaeylfqtx7yfm6i@aching.in.mat.cc>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, On 3/16/21 6:19 PM, Mathieu Arnold wrote: > > The rationale being that given X ports that depend on a node module, you > will probably need more than X versions of that module because they > will all depend on incompatible versions of said module. I think this applies to Go modules as well. It might be good to document this, if it isn't already. Maybe other things too, like Rust, etc? Even with python/ruby etc. there's a lot of need for multiple versions, but I guess it's not as much. > A port that requires node modules must provide its own. It can > absolutely be by having an extra step for the maintainer to generate a > tarball with all the required modules that can simply be extracted as > needed. I have not checked, but there are probably ports already doing > this. > Which leads to the point that since ports/Mk/Uses/go.mk provides a way to do this, maybe ports/Mk/Uses/node.mk should as well? Just a thought. Cheers, Steve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?80fc0f66-44b1-f7d3-fc36-b78d63bc753b>