Re: Naming of node packages with @ and /

[Julien Lepiller <julien@lepiller.eu>]

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 
>> <swedebugia@riseup.net <mailto:swedebugia@riseup.net>> 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?