From mboxrd@z Thu Jan 1 00:00:00 1970 From: swedebugia Subject: Re: Naming of node packages with @ and / Date: Wed, 28 Nov 2018 21:34:48 +0100 Message-ID: <33ab0b8f-618f-397a-981e-4b1889494d59@riseup.net> References: <6d747c3a-af63-c222-c913-3355be92ac43@riseup.net> <3a63c5bc9111b26d48df1d40e62bac79@lepiller.eu> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:47686) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gS6Xx-0002eU-H3 for guix-devel@gnu.org; Wed, 28 Nov 2018 15:34:58 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gS6Xs-0006t0-Uq for guix-devel@gnu.org; Wed, 28 Nov 2018 15:34:57 -0500 Received: from mx1.riseup.net ([198.252.153.129]:48964) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1gS6Xs-0006rv-LB for guix-devel@gnu.org; Wed, 28 Nov 2018 15:34:52 -0500 In-Reply-To: <3a63c5bc9111b26d48df1d40e62bac79@lepiller.eu> Content-Language: en-US List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Julien Lepiller , guix-devel@gnu.org On 2018-11-28 13:46, Julien Lepiller wrote: > Le 2018-11-28 12:21, swedebugia a =C3=A9crit=C2=A0: >> On 2018-11-28 00:10, Catonano wrote: >>> >>> >>> Il giorno mar 27 nov 2018 alle ore 21:58 swedebugia=20 >>> > ha scritto: >>> >>> =C2=A0=C2=A0=C2=A0 Hi >>> >>> =C2=A0=C2=A0=C2=A0 There are some crazy naming going on in the node-c= ommunity. How=20 >>> do we >>> =C2=A0=C2=A0=C2=A0 deal with this? >>> >>> =C2=A0=C2=A0=C2=A0 Note: there is another package called "babel-core"= so just >>> =C2=A0=C2=A0=C2=A0 stripping/replacing the weird characters won't wor= k well. >>> >>> =C2=A0=C2=A0=C2=A0 Any ideas? >> snip >> >>> I think those are the so called "scoped packages" >>> >>> https://docs.npmjs.com/misc/scope >>> >>> https://nitayneeman.com/posts/understanding-scoped-packages-in-npm/ >> >> Aha! This makes sense. The importer and guix package will have to=20 >> handle this. >> >> E.g. this way: >> >> guix import npm -S babel babe-core >> where -S is "scope". >> >> We will probably have to add a field or property to our (package) >> record stating that it is part of a scope: >> (properties >> `((scope . babel))) >> >> guix package will have to support it too: >> guix package -i -S babel babel-core >> >> What do you think? Any better ways to handle this? >=20 > Do we have to bother with scope? Can't we simply import the package lik= e=20 > so: >=20 > guix import npm @babel/babel-core >=20 > and install the corresponding package with >=20 > guix package -i bable/bable-core >=20 > I don't like the idea of adding this notion of scope to guix, unless we= =20 > really need it for something? We can do that. It is simpler. Won't the "/" interfere with something, e.g. the scripts for updating=20 packages? We will have to adapt those perhaps but that is doable. Effectively you suggest we strip the @ in the guix-name procedure in=20 npm.scm and keep the rest intact. --=20 Cheers Swedebugia