From mboxrd@z Thu Jan 1 00:00:00 1970 From: Julien Lepiller Subject: Re: Naming of node packages with @ and / Date: Wed, 28 Nov 2018 13:46:12 +0100 Message-ID: <3a63c5bc9111b26d48df1d40e62bac79@lepiller.eu> References: <6d747c3a-af63-c222-c913-3355be92ac43@riseup.net> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:41918) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gRzES-00047r-Rf for guix-devel@gnu.org; Wed, 28 Nov 2018 07:46:25 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gRzEO-0003s2-Gv for guix-devel@gnu.org; Wed, 28 Nov 2018 07:46:20 -0500 Received: from lepiller.eu ([2a00:5884:8208::1]:36888) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1gRzEO-0003gM-8J for guix-devel@gnu.org; Wed, 28 Nov 2018 07:46:16 -0500 Received: from webmail.lepiller.eu (static-176-182-42-79.ncc.abo.bbox.fr [176.182.42.79]) by lepiller.eu (OpenSMTPD) with ESMTPSA id 95df78c5 (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256:NO) for ; Wed, 28 Nov 2018 12:43:45 +0000 (UTC) In-Reply-To: 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: guix-devel@gnu.org Le 2018-11-28 12:21, swedebugia a écrit : > On 2018-11-28 00:10, Catonano wrote: >> >> >> Il giorno mar 27 nov 2018 alle ore 21:58 swedebugia >> > ha scritto: >> >> Hi >> >> There are some crazy naming going on in the node-community. How do >> we >> deal with this? >> >> Note: there is another package called "babel-core" so just >> stripping/replacing the weird characters won't work well. >> >> 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 > 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? Do we have to bother with scope? Can't we simply import the package like so: guix import npm @babel/babel-core and install the corresponding package with guix package -i bable/bable-core I don't like the idea of adding this notion of scope to guix, unless we really need it for something?