unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andreas Enge <andreas@enge.fr>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org, Nicolas Goaziou <mail@nicolasgoaziou.fr>
Subject: Re: 01/01: gnu: Add ratpoints.
Date: Thu, 20 Jun 2019 12:51:11 +0200	[thread overview]
Message-ID: <20190620105111.GA16842@jurong> (raw)
In-Reply-To: <87zhmcmxuk.fsf@gnu.org>

On Thu, Jun 20, 2019 at 11:04:35AM +0200, Ludovic Courtès wrote:
> > +++ b/gnu/packages/patches/ratpoints-sturm_and_rp_private.patch
> Could you add a sentence or two explaining what the patch does and what
> its upstream status is?  This is especially important for non-trivial
> patches like this one.

Nobody knows :-)  The patch appears without further comments in the Sage
build system.

The upstream code has not changed since 2011, something I have been seeing
a lot over the last few days with seemingly abandoned mathematics code, but
which is not dropped since it is still the most efficient implementation
for solving a given problem. Luckily this one is C, the C++ packages often
do not even compile anymore without specific patches from the Sage project.

In this case, there is hope though, from SPKG.txt:
"NOTE: the ratpoints package has been assimilated by PARI/GP. Therefore,
this package (as Sage package) is deprecated. In the future, it will be
removed from Sage."

So maybe we could move it (again, sorry...), to the sagemath module,
with the plan to drop it as soon as Sage does not need it anymore?

Andreas

  reply	other threads:[~2019-06-20 10:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20190619194512.20737.92090@vcs0.savannah.gnu.org>
     [not found] ` <20190619194514.7AA93209BF@vcs0.savannah.gnu.org>
2019-06-20  9:04   ` 01/01: gnu: Add ratpoints Ludovic Courtès
2019-06-20 10:51     ` Andreas Enge [this message]
2019-06-21 20:58       ` Nicolas Goaziou

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=20190620105111.GA16842@jurong \
    --to=andreas@enge.fr \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    --cc=mail@nicolasgoaziou.fr \
    /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).