unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Guix Devel <guix-devel@gnu.org>
Subject: Re: Licensing issue with Gmsh?
Date: Fri, 2 Oct 2020 14:28:40 +0200	[thread overview]
Message-ID: <CAJ3okZ39XONDdbbre0P-QiPCPyiRsE34iUJGsCGY0A40CQZzeA@mail.gmail.com> (raw)
In-Reply-To: <86lfgp3vae.fsf@gmail.com>

Dear,

On Fri, 2 Oct 2020 at 10:07, zimoun <zimon.toutoune@gmail.com> wrote:

> --8<---------------cut here---------------start------------->8---
>       (snippet
>        ;; Remove non-free METIS code
>        '(begin
>           (delete-file-recursively "contrib/metis")
>           #t))))
> --8<---------------cut here---------------end--------------->8---

[...]

> I am inclined to enable METIS because it appears to me fine.  However,
> since freedom is essential, it would like another advice and/or comment
> on.

Gmsh had updated from METIS 4 (non-free) to METIS 5 (free) in commit
eaff7f6477fe876991615cfa4b5832bd5f12994b.

<https://gitlab.onelab.info/gmsh/gmsh/-/commit/eaff7f6477fe876991615cfa4b5832bd5f12994b>

The current Gmsh version 2.16.0 had been released on the Jan. 3rd and
the commit updating METIS 4->5 on the Sept., 19th.


All the best,
simon


  reply	other threads:[~2020-10-02 12:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-02  8:07 Licensing issue with Gmsh? zimoun
2020-10-02 12:28 ` zimoun [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-10-02 16:26 Paul Garlick
2020-10-02 17:35 ` zimoun
2020-10-02 21:59   ` Paul Garlick
2020-10-02 23:49     ` zimoun

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=CAJ3okZ39XONDdbbre0P-QiPCPyiRsE34iUJGsCGY0A40CQZzeA@mail.gmail.com \
    --to=zimon.toutoune@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).