Move PARI databases out of PARI package

[jdemeyer]

The PARI package in Sage contains two databases (galdata and seadata-small). These should be separated and the packaging simplified.

Upstream (all these are simply repacked/renamed upstream tarballs):

• http://boxen.math.washington.edu/home/jdemeyer/spkg/pari-2.5.5b.tar.bz2
• http://boxen.math.washington.edu/home/jdemeyer/spkg/pari_galdata-20080411.tar.bz2
• http://boxen.math.washington.edu/home/jdemeyer/spkg/pari_seadata_small-20090618.tar.bz2

CC: @jpflori @pjbruin

Component: packages: standard

Author: Jeroen Demeyer

Branch/Commit: u/jdemeyer/ticket/15765 @ 1678b89

Reviewer: Peter Bruin

Issue created by migration from https://trac.sagemath.org/ticket/15765

[jdemeyer]

Branch: u/jdemeyer/ticket/15765

[jdemeyer]

Commit: ad63daf

[jdemeyer]

New commits:

ad63daf

Move PARI databases out of PARI package

[pjbruin]

comment:7

Nice restructuring, builds without problems, passes all tests.

[pjbruin]

Reviewer: Peter Bruin

[vbraun]

comment:8

We already have a pari-2.5.5.tar.bz2 tarball. Since it is checksummed we can't replace it without breaking other builds. This shoud be done in conjuction with the next Pari update.

[jdemeyer]

comment:10

Since it will simplify the next upgrade, why not simply rename the tarball to something else? Can we call it pari-2.5.5b.tar.bz2 or something?

[vbraun]

comment:11

That would work, too. But you can simplify the next upgrade just as well by starting with this branch.

[jdemeyer]

comment:12

Replying to @vbraun:

That would work, too. But you can simplify the next upgrade just as well by starting with this branch.

But less so, since the probability of merge conflicts (I just resolved one) increases the longer that this branch does not get merged. And other people who want to work on PARI might not know about this ticket.

[sagetrac-git]

Branch pushed to git repo; I updated commit sha1. New commits:

1678b89

Merge remote-tracking branch 'origin/develop' into ticket/15765

[sagetrac-git]

Changed commit from ad63daf to 1678b89

[pjbruin]

comment:16

I did notice that the new pari-2.5.5.tar.bz2 had the same name but a different checksum, but didn't run into problems because I downloaded the new one by hand before checking out this branch. Should have tried harder to play the unsuspecting user... 8-)