From: tornaria <tornaria@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Update pari optional packages
Date: Sat, 30 Oct 2021 22:10:51 +0200 [thread overview]
Message-ID: <20211030201051.rA3VboLWmoHuCY_fuoREsafCvYfokTQy2ImSnf3GcMU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32641@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1131 bytes --]
New comment by tornaria on void-packages repository
https://github.com/void-linux/void-packages/pull/32641#issuecomment-955586377
Comment:
@ericonr: thanks for merging #29997. What about this one next? It's an itch I have, since I use pari-gp a lot (literally daily, for my work).
I know this includes several changes, but there are 6 different optional data packages and all templates follow the same structure. Each change is documented in the respective commit as a bullet list.
Besides `pari-elldata` update and adding two new packages (always with the same template structure), the only thing that changes in the installed files is that datafiles are compressed when it makes sense (for files larger than 4k) saving a lot of installed-size. For large packages a `<PKG>-small` package is split out which contains a reasonable minimal portion of the database (e.g. enough to pass tests) but installing `<PKG>` after this is equivalent to installing `<PKG>` before this.
Note that @dkwo and @motorto already reviewed this PR and gave :+1: above. Nothing changed here since then other than rebasing for pari updates.
next prev parent reply other threads:[~2021-10-30 20:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-23 2:13 [PR PATCH] " tornaria
2021-08-23 23:03 ` [PR PATCH] [Updated] " tornaria
2021-08-23 23:04 ` tornaria
2021-08-24 21:13 ` tornaria
2021-08-25 7:41 ` dkwo
2021-08-25 7:43 ` dkwo
2021-08-26 15:58 ` [PR PATCH] [Updated] " tornaria
2021-08-26 16:00 ` tornaria
2021-09-04 14:55 ` motorto
2021-09-04 16:08 ` tornaria
2021-09-04 17:33 ` motorto
2021-09-04 19:14 ` [PR PATCH] [Updated] " tornaria
2021-09-04 19:24 ` tornaria
2021-09-06 9:32 ` dkwo
2021-10-27 2:09 ` [PR PATCH] [Updated] " tornaria
2021-10-27 2:12 ` tornaria
2021-10-30 20:10 ` tornaria [this message]
2021-10-30 20:17 ` ericonr
2021-11-09 16:00 ` [PR PATCH] [Merged]: " leahneukirchen
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=20211030201051.rA3VboLWmoHuCY_fuoREsafCvYfokTQy2ImSnf3GcMU@z \
--to=tornaria@users.noreply.github.com \
--cc=ml@inbox.vuxu.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 NNTP newsgroup(s).