From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Andrea Frigido <andrea.frigido@gmail.com>
Cc: 33431-done@debbugs.gnu.org
Subject: bug#33431: [PATCH] gnu: Add yarn
Date: Tue, 13 Jul 2021 09:10:00 -0400 [thread overview]
Message-ID: <87im1es6l3.fsf_-_@gmail.com> (raw)
In-Reply-To: <CAHN_qaq7=DZ1avmJ23W+oDAWNuKWX_MRjfbpZLXa5jkoTLsADQ@mail.gmail.com> (Andrea Frigido's message of "Mon, 10 Dec 2018 08:24:55 +0000")
Hello Andrea,
Andrea Frigido <andrea.frigido@gmail.com> writes:
> Hi Jelle,
> thank for the review.
>
> The tarball comes from the official releases page of yarn:
> https://github.com/yarnpkg/yarn/releases
> I followed the same process of the nix package:
> https://github.com/NixOS/nixpkgs/blob/1a4498d1328e8dd74a8099f16972224c87d01358/pkgs/development/tools/yarn/default.nix#L23
>
> I thought it was an acceptable way of packaging this software.
Nix doesn't commit to offer only free software, for one.
> Is there a policy in Guix about this that I need to follow?
The policy for GNU Guix is that of the GNU Free Software Distribution
Guidelines (FSDG) [0]. We also typically do the utmost to fully
bootstrap things from sources, compared to other distributions.
Its seems the issues raised by Jelle are blocking progress on this
package submission. Babel seems a complicated piece of software that
will take some effort to get packaged in Guix.
I'll close this ticket as it is not actionable and probably won't be in
the near future.
Please resubmit when the missing packages to fully build from sources
have been added.
Thank you!
Maxim
prev parent reply other threads:[~2021-07-13 13:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-19 13:57 [bug#33431] [PATCH] gnu: Add yarn Andrea Frigido
2018-11-19 18:06 ` Andrea Frigido
2018-12-08 13:17 ` Andrea Frigido
2018-12-08 15:07 ` Jelle Licht
2018-12-10 8:24 ` Andrea Frigido
2021-07-13 13:10 ` Maxim Cournoyer [this message]
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=87im1es6l3.fsf_-_@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=33431-done@debbugs.gnu.org \
--cc=andrea.frigido@gmail.com \
/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).