From: ludo@gnu.org (Ludovic Courtès)
To: guix-devel@gnu.org
Subject: Re: patches question
Date: Fri, 24 Jun 2016 14:09:39 +0200 [thread overview]
Message-ID: <87a8ia7pq4.fsf@gnu.org> (raw)
In-Reply-To: <20160623132347.GA9193@shadowwalker> (ng0@we.make.ritual.n0.is's message of "Thu, 23 Jun 2016 13:23:47 +0000")
Hello!
ng0 <ng0@we.make.ritual.n0.is> skribis:
> diff --git a/config/Makefile.in b/config/Makefile.in
> --- a/config/Makefile.in
> +++ b/config/Makefile.in
I view this patch as upstream work that Guix should not carry. To put
it differently, it’s not Guix’s missing to maintain a fork of Firefox
(or any other package).
> (define-public firefox
> (package
> (name "firefox")
> (version "45.2.0esr")
What is the goal here?
Guix proper can provide IceCat (which modifies Firefox to comply with
trademark rules, to comply with the GNU FSDG¹, and to enhance privacy),
maybe Tor Browser (assuming it complies with the FSDG as well), but not
stock Firefox (unless the trademark issue and FSDG violations are
resolved.)
Besides, I think it should be possible to (inherit icecat) rather than
duplicate all the recipe.
Hope this clarifies things!
Thanks,
Ludo’.
¹ https://www.gnu.org/distros/free-system-distribution-guidelines.html
next prev parent reply other threads:[~2016-06-24 12:09 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-23 10:41 patches question ng0
2016-06-23 11:09 ` Andreas Enge
2016-06-23 11:30 ` ng0
2016-06-23 20:14 ` Andreas Enge
2016-06-23 22:18 ` ng0
2016-06-23 13:23 ` ng0
2016-06-23 20:27 ` Andreas Enge
2016-06-24 12:09 ` Ludovic Courtès [this message]
2016-06-24 13:43 ` ng0
2016-06-24 15:48 ` Tor Browser Ludovic Courtès
2016-06-24 17:49 ` ng0
2016-06-26 10:05 ` Ludovic Courtès
2016-06-29 12:48 ` ng0
2016-06-30 10:29 ` Ludovic Courtès
2016-06-30 16:09 ` ng0
2016-06-30 18:00 ` ng0
2016-08-05 13:35 ` ng0
2016-08-06 4:05 ` Alex Vong
2016-08-06 11:14 ` ng0
2016-08-08 8:03 ` Alex Vong
2016-08-10 20:01 ` Mark H Weaver
2016-08-11 8:51 ` ng0
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=87a8ia7pq4.fsf@gnu.org \
--to=ludo@gnu.org \
--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 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.