Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 16 May 2017 12:22:47 +0200
From:      "Bradley T. Hughes" <bradleythughes@fastmail.fm>
To:        Rodrigo Osorio <ros@bebik.net>
Cc:        freebsd-ports@freebsd.org
Subject:   Re: How should we name node-js ports ?
Message-ID:  <155F7AD7-95F8-447A-A052-C29396B53245@fastmail.fm>
In-Reply-To: <5254fffe-b0e1-5912-c868-9057369da9ef@bebik.net>
References:  <ba4cd1f6-2bd7-f710-2e6c-56c470c5ef7d@bebik.net> <32cbf11f-5ce0-ce16-8c56-c45d585ed2f6@FreeBSD.org> <53BBD762-9A8B-4582-B65D-27D752B567BF@adamw.org> <5254fffe-b0e1-5912-c868-9057369da9ef@bebik.net>

next in thread | previous in thread | raw e-mail | index | archive | help

> On 15 May 2017, at 20:22, Rodrigo Osorio <ros@bebik.net> wrote:
>=20
>=20
> Hi Adam,
>=20
> Thanks for your feedback.
>=20
> On 05/15/17 18:52, Adam Weinberger wrote:
>>> On 15 May, 2017, at 6:57, Ruslan Makhmatkhanov <rm@FreeBSD.org> =
wrote:
>>>=20
>>>=20
>>> npm packages can be installed by yarn as well; nodejs is really the =
common name and makes a better prefix.
>>>=20
>>> 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.

I agree with this sentiment. It also does not sit well with me to use =
one package manager (pkg) to run another package manager (npm) to =
install dependencies.

In my expereince, Node.js apps tend to have their dependencies installed =
locally, as it is too easy to get into conflicts or incompatibilities =
with globally installed versions.  The exception to the rule is for =
things that install a runnable command, like grunt-cli, npm, mocha, and =
so on.

>>> 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.

Like expressed above, I think the "remains available to other and can be =
reused as dependencies for others" can be more harmful than helpful.

--
Bradley T. Hughes
bradleythughes@fastmail.fm




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?155F7AD7-95F8-447A-A052-C29396B53245>