From: swedebugia <swedebugia@riseup.net>
To: Catonano <catonano@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Naming of node packages with @ and /
Date: Wed, 28 Nov 2018 12:21:59 +0100 [thread overview]
Message-ID: <fafd0b30-5c39-57aa-9c63-8febe2e0898e@riseup.net> (raw)
In-Reply-To: <CAJ98PDzM_MMrs0RntdsG_RsXKBOO5keaY8AUCBE1cBMUY6BG+g@mail.gmail.com>
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?
--
Cheers
Swedebugia
next prev parent reply other threads:[~2018-11-28 11:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-27 21:02 Naming of node packages with @ and / swedebugia
2018-11-27 23:10 ` Catonano
2018-11-28 11:21 ` swedebugia [this message]
2018-11-28 12:46 ` Julien Lepiller
2018-11-28 20:34 ` swedebugia
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fafd0b30-5c39-57aa-9c63-8febe2e0898e@riseup.net \
--to=swedebugia@riseup.net \
--cc=catonano@gmail.com \
--cc=guix-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).