From: Maxime Devos <maximedevos@telenet.be>
To: burning2007@ya.ru,
Liliana Marie Prikler <liliana.prikler@gmail.com>,
"55790@debbugs.gnu.org" <55790@debbugs.gnu.org>
Subject: [bug#55790] [PATCH 0/1] Add chromium-web-store extension
Date: Sat, 04 Jun 2022 15:08:33 +0200 [thread overview]
Message-ID: <d221316e470b9977b6e875e83287a7febe735c05.camel@telenet.be> (raw)
In-Reply-To: <223771654342162@mail.yandex.ru>
[-- Attachment #1: Type: text/plain, Size: 761 bytes --]
[Removed anthony@example.com from CC because it's not a valid e-mail address]
burning2007@ya.ru schreef op za 04-06-2022 om 14:30 [+0300]:
> > refer to the FSDG [1], particularly "... no specific recipes for
> > installation of particular nonfree programs ..."
>
> Does it mean that a package proposed for inclusion shouldn't provide
> a way to install other software from external "repository",
External repositories are ok I think, no need to remove pip from Python
or ContentDB from Minetest or channels or "guix build -f" from Guix or
cabal.
> like Chrome Web Store?
Chrome Web Store is not just an external repository, it's a mostly non-
free repository (in contrast to, say, pypi, ContentDB), see my e-mail.
Greetings,
Maxime
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-06-04 13:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-04 1:02 [bug#55790] [PATCH 0/1] Add chromium-web-store extension burning2007
2022-06-04 8:28 ` [bug#55790] [PATCH 1/1] gnu: browser-extensions: add chromium-web-store burning2007
2022-06-04 8:48 ` [bug#55790] [PATCH 0/1] Add chromium-web-store extension Liliana Marie Prikler
2022-06-04 11:28 ` burning2007
2022-06-04 11:30 ` burning2007
2022-06-04 13:08 ` Maxime Devos [this message]
2022-06-04 13:09 ` Maxime Devos
2024-03-11 19:39 ` Skyler Ferris via Guix-patches via
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d221316e470b9977b6e875e83287a7febe735c05.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=55790@debbugs.gnu.org \
--cc=burning2007@ya.ru \
--cc=liliana.prikler@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.