Date: Mon, 15 May 2017 20:22:43 +0200 From: Rodrigo Osorio <ros@bebik.net> To: freebsd-ports@freebsd.org Subject: Re: How should we name node-js ports ? Message-ID: <5254fffe-b0e1-5912-c868-9057369da9ef@bebik.net> In-Reply-To: <53BBD762-9A8B-4582-B65D-27D752B567BF@adamw.org> References: <ba4cd1f6-2bd7-f710-2e6c-56c470c5ef7d@bebik.net> <32cbf11f-5ce0-ce16-8c56-c45d585ed2f6@FreeBSD.org> <53BBD762-9A8B-4582-B65D-27D752B567BF@adamw.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Adam, Thanks for your feedback. On 05/15/17 18:52, Adam Weinberger wrote: >> On 15 May, 2017, at 6:57, Ruslan Makhmatkhanov <rm@FreeBSD.org> wrote: >> >> >> npm packages can be installed by yarn as well; nodejs is really the common name and makes a better prefix. >> >> That said, making node ports does not sit well with me. npm/yarn manages node packages. Things will break if a user has those same packages installed globally and tries to update or remove them, or if a user needs specific global versions installed. >> >> Rodrigo, I think your better option is simply to bundle those dependencies yourself, at the specific versions that your port requires, and install them to a private location. I decide to split the dependencies in several packages and I use npm a short perform the package installation before the staging. That way node packages remains available to other and can be reused as dependencies for others node ports. > > # Adam > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5254fffe-b0e1-5912-c868-9057369da9ef>