From: zimoun <zimon.toutoune@gmail.com>
To: Paul Garlick <pgarlick@tourbillion-technology.com>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Licensing issue with Gmsh?
Date: Fri, 2 Oct 2020 19:35:58 +0200 [thread overview]
Message-ID: <CAJ3okZ2iFXc2px++dM=Y0HR3qXjw6QaE3iPn+cSFdTM9CtS7Sw@mail.gmail.com> (raw)
In-Reply-To: <d63fcf37e8d742a9f1521c8d45eaa015cb1d700d.camel@tourbillion-technology.com>
Dear Paul,
On Fri, 2 Oct 2020 at 18:26, Paul Garlick
<pgarlick@tourbillion-technology.com> wrote:
> Thank you for working on the Gmsh package. There have been a great
> many changes since the last update.
Yeah, the Christophe's talk at last FOSDEM was exciting about the new
features in 4.x. ;-)
And since the Guix v1.2 is in the pipe...
> There is a distinction between METIS (free) and ParMETIS (non-free)
> which may have influenced the decision to remove the whole metis
> directory. As far as I can see Gmsh does not use any files from the
> ParMETIS library.
That's what Christophe (Geuzaine) told me. Cool!
> There is only a parmetis.c file included in the metis directory.
> However, it is commented out in CMakeLists.txt.
Here [1] the patch updating Gmsh. Well, I missed this file (the base
code changed a lot since last time I was playing with; ~2012-2016),
thank you for explaining.
To be "Guix compliant", this parametis.c file should be removed, right?
[1] <http://issues.guix.gnu.org/issue/43761>
All the best,
simon
next prev parent reply other threads:[~2020-10-02 17:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-02 16:26 Licensing issue with Gmsh? Paul Garlick
2020-10-02 17:35 ` zimoun [this message]
2020-10-02 21:59 ` Paul Garlick
2020-10-02 23:49 ` zimoun
-- strict thread matches above, loose matches on Subject: below --
2020-10-02 8:07 zimoun
2020-10-02 12:28 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJ3okZ2iFXc2px++dM=Y0HR3qXjw6QaE3iPn+cSFdTM9CtS7Sw@mail.gmail.com' \
--to=zimon.toutoune@gmail.com \
--cc=guix-devel@gnu.org \
--cc=pgarlick@tourbillion-technology.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.