From: Florian Paul Schmidt <mista.tapas@gmx.net>
To: "Thompson, David" <dthompson2@worcester.edu>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: General Question: Execution of binaries not built for GuixSD
Date: Wed, 22 Jun 2016 16:12:06 +0200 [thread overview]
Message-ID: <576A9CB6.80508@gmx.net> (raw)
In-Reply-To: <CAJ=RwfZSz3GOC9zbp+dVawFm1AgV=r2Wg+w6ersiqauXpsmxwQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1343 bytes --]
On 06/22/2016 03:53 PM, Thompson, David wrote:
> On Wed, Jun 22, 2016 at 9:27 AM, Florian Paul Schmidt
> <mista.tapas@gmx.net> wrote:
>> See the attached file for reference. Put it into a guix checkout under
>>
>> nonfree/packages/
>>
>> Does that help as a starting point?
>
> Do the upstream Firefox and/or Thunderbird contain nonfree components?
> If so, please do not promote such software on this list.
>
> I really really really cannot recommend this approach to packaging,
> because it goes against one of the core properties of Guix:
> reproducibility. Taking someone else's binary and hacking it until it
> works isn't a real solution. The proper way to do this is to build
> binaries from source that are compatible with Guix.
I'm answering a technical question, not promoting the use of this
software, also I'm fully aware of the caveats you mentioned. I didn't
deem it worthy to reiterate them.
Even if you do consider it promotion I think it's a far stretch from an
email of a participant in a list to the guix project itself promoting
these kinds of solutions.
Also you can consider this email as a test case for the policies the
Guix project has in place :) How you want to deal with it, etc :) Have
at it (/me puts on his flame retardant suite)!
Regards,
Flo
--
https://fps.io
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-06-22 14:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-21 23:21 General Question: Execution of binaries not built for GuixSD christoph vogelsberg
2016-06-22 10:50 ` Florian Paul Schmidt
2016-06-22 13:27 ` Florian Paul Schmidt
2016-06-22 13:53 ` Thompson, David
2016-06-22 14:06 ` ng0
2016-06-22 14:12 ` Florian Paul Schmidt [this message]
2016-06-22 12:44 ` Thompson, David
2016-06-24 18:19 ` General Question: What if Binary Building breaks? christoph vogelsberg
2016-06-24 18:55 ` ng0
2016-06-25 17:36 ` Leo Famulari
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=576A9CB6.80508@gmx.net \
--to=mista.tapas@gmx.net \
--cc=dthompson2@worcester.edu \
--cc=help-guix@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.
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).