From: sgn <sgn@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Pari optional packages
Date: Wed, 02 Sep 2020 03:58:56 +0200 [thread overview]
Message-ID: <20200902015856.DF9vw0OuG1zc65myTXanU8jeVlaA_8arNTzvD2bZ7gs@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24371@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 800 bytes --]
New comment by sgn on void-packages repository
https://github.com/void-linux/void-packages/pull/24371#issuecomment-685236507
Comment:
On 2020-09-01 11:58:54-0700, André Cerqueira <notifications@github.com> wrote:
> @Piraty and @sgn
>
> I have looked at the source files and seadata-small only has 2 files
> (sea0 and sea2) , this files are packaged with seadata.
>
> seadata-big brings only sea**.gz files that don't exist on seadata "normal" .
>
> So would it be okay to only package seadata and seadata-big
> (separated package) and remove the seadata-small (is "redundant" the
> only advantage is the size of seadata-small [655 KB] compared to
> seadata [18.3 MB] , which nowadays I think is not a necessity
> anymore).
Let's just package seadata and seadata-big, no sub-pkg.
--
Danh
next prev parent reply other threads:[~2020-09-02 1:58 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-19 21:01 [PR PATCH] " motorto
2020-08-19 21:20 ` [PR PATCH] [Closed]: " motorto
2020-08-19 21:20 ` [PR PATCH] [Updated] " motorto
2020-08-19 21:28 ` motorto
2020-08-19 21:32 ` motorto
2020-08-20 12:09 ` sgn
2020-08-20 12:37 ` motorto
2020-08-20 12:38 ` motorto
2020-08-21 8:59 ` dkwo
2020-08-21 9:01 ` dkwo
2020-08-21 9:28 ` motorto
2020-08-21 9:44 ` motorto
2020-08-21 10:13 ` [PR PATCH] [Updated] " motorto
2020-08-21 11:29 ` dkwo
2020-08-21 11:52 ` motorto
2020-08-21 11:59 ` motorto
2020-08-31 18:48 ` [PR REVIEW] " Piraty
2020-08-31 19:35 ` motorto
2020-08-31 20:33 ` motorto
2020-08-31 20:33 ` motorto
2020-09-01 4:27 ` sgn
2020-09-01 4:28 ` sgn
2020-09-01 7:21 ` [PR REVIEW] " Piraty
2020-09-01 7:30 ` sgn
2020-09-01 9:48 ` Piraty
2020-09-01 10:16 ` [PR PATCH] [Updated] " motorto
2020-09-01 10:21 ` [PR REVIEW] " motorto
2020-09-01 11:04 ` motorto
2020-09-01 11:06 ` motorto
2020-09-01 18:51 ` motorto
2020-09-01 18:58 ` motorto
2020-09-01 18:58 ` motorto
2020-09-01 19:00 ` [PR REVIEW] " motorto
2020-09-02 1:58 ` sgn [this message]
2020-09-02 8:59 ` [PR PATCH] [Updated] " motorto
2020-09-02 14:17 ` motorto
2020-09-02 14:19 ` motorto
2020-09-02 15:35 ` [PR PATCH] [Updated] " motorto
2020-09-04 20:10 ` motorto
2020-09-14 21:38 ` motorto
2020-09-14 22:00 ` sgn
2020-09-15 8:36 ` motorto
2020-09-15 8:39 ` motorto
2020-09-15 8:52 ` [PR PATCH] [Updated] " motorto
2020-09-15 8:53 ` motorto
2020-09-15 10:12 ` [PR PATCH] [Closed]: " Piraty
2020-09-15 11:59 ` dkwo
2020-09-15 11:59 ` dkwo
2020-09-15 12:00 ` dkwo
2020-09-15 12:35 ` dkwo
2020-09-16 14:32 ` dkwo
2020-09-16 17:57 ` motorto
2020-09-16 18:46 ` motorto
2020-09-16 20:30 ` motorto
2020-09-17 1:01 ` sgn
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=20200902015856.DF9vw0OuG1zc65myTXanU8jeVlaA_8arNTzvD2bZ7gs@z \
--to=sgn@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).