From owner-freebsd-ports@freebsd.org  Mon May 15 16:52:57 2017
Return-Path: <owner-freebsd-ports@freebsd.org>
Delivered-To: freebsd-ports@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9EF52D6E6C8
 for <freebsd-ports@mailman.ysv.freebsd.org>;
 Mon, 15 May 2017 16:52:57 +0000 (UTC) (envelope-from adamw@adamw.org)
Received: from apnoea.adamw.org (apnoea.adamw.org [104.225.5.94])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "apnoea.adamw.org",
 Issuer "Let's Encrypt Authority X3" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id B6F26165;
 Mon, 15 May 2017 16:52:56 +0000 (UTC) (envelope-from adamw@adamw.org)
Received: by apnoea.adamw.org (OpenSMTPD) with ESMTPSA id 700c1e9d
 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO;
 Mon, 15 May 2017 10:52:55 -0600 (MDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: How should we name node-js ports ?
From: Adam Weinberger <adamw@adamw.org>
In-Reply-To: <32cbf11f-5ce0-ce16-8c56-c45d585ed2f6@FreeBSD.org>
Date: Mon, 15 May 2017 10:52:53 -0600
Cc: Rodrigo Osorio <ros@bebik.net>, freebsd-ports@freebsd.org,
 portmgr@FreeBSD.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <53BBD762-9A8B-4582-B65D-27D752B567BF@adamw.org>
References: <ba4cd1f6-2bd7-f710-2e6c-56c470c5ef7d@bebik.net>
 <32cbf11f-5ce0-ce16-8c56-c45d585ed2f6@FreeBSD.org>
To: Ruslan Makhmatkhanov <rm@FreeBSD.org>
X-Mailer: Apple Mail (2.3273)
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports/>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 15 May 2017 16:52:57 -0000

> On 15 May, 2017, at 6:57, Ruslan Makhmatkhanov <rm@FreeBSD.org> wrote:
>=20
> Rodrigo Osorio wrote on 05/14/2017 15:16:
>> Hi,
>> I have a bunch of nodejs ports to add, most of them as dependencies,
>> and I wonder if we can find a naming standard like adding  'node' or
>> 'node-js' prefix in the name ; I personally prefer 'node'.
>> As a result a port who install the node package xxx will be named =
'node-xxx'
>> Does it sounds good to you ?
>> Thanks for your time,
>> -- rodrigo
>=20
> Am I right they will be actually installed with npm? If so, it would =
make sense to name them npm-<package>, like rubygems installed packages.

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.

# Adam


--=20
Adam Weinberger
adamw@adamw.org
https://www.adamw.org