From: tornaria <tornaria@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Package request: SageMath
Date: Fri, 20 Aug 2021 14:06:31 +0200 [thread overview]
Message-ID: <20210820120631.lhsjdEnETQvoD54w0MW8UxAyD_6jj5AP5Py6dKsAWKU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-19090@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1410 bytes --]
New comment by tornaria on void-packages repository
https://github.com/void-linux/void-packages/issues/19090#issuecomment-902644831
Comment:
> I would like to try to package sage, but I'm quite new to void. Where should I start?
It's a long road, we are slowly packaging dependencies but it will take some time.
It could be useful if you can test and review some pending PR: #29997, #30034, #30035, #30036.
If you merge those 4 PR, then you can compile sage with all of them installed (FlintQS, lcalc-devel, mpfi-devel, givaro-devel, fflas_ffpack, linbox-devel). The more dependencies we have, fewer have to be compiled by sage. Other recently merged dependencies that you may want to install are: gp2c, gf2x-devel, ntl-devel, flintlib-devel, arb-devel, eclib-devel. At this point I can have sage-9.4.rc2 compiled in ~ 25 min with -j8. More important, all those dependencies can now be used for other purposes.
I suggest that you focus on one or two packages and try to get them in good shape, pass QA, and get merged. It will take some time, but in my experience it's not a good idea to make too many half-baked PR at the same time. For example: try to get your lean-community package merged, and try to package m4ri and m4rie (both in one PR since they depend). Learn from that, e.g. how to test your templates in -musl and -i686, and also how to try cross compilation to see if it works, etc.
next prev parent reply other threads:[~2021-08-20 12:06 UTC|newest]
Thread overview: 129+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-13 9:20 [ISSUE] " voidlinux-github
2020-02-13 19:20 ` voidlinux-github
2020-02-14 9:02 ` voidlinux-github
2020-08-26 12:03 ` dkwo
2020-09-02 9:08 ` motorto
2020-09-02 9:28 ` dkwo
2020-09-02 9:31 ` dkwo
2020-09-06 7:20 ` dkwo
2020-09-06 7:23 ` dkwo
2020-09-06 7:40 ` dkwo
2020-09-06 7:40 ` dkwo
2020-09-06 7:40 ` dkwo
2020-09-06 7:43 ` dkwo
2020-09-06 7:47 ` dkwo
2020-09-06 7:47 ` dkwo
2020-09-06 7:52 ` dkwo
2020-09-06 7:53 ` dkwo
2020-09-06 7:54 ` dkwo
2020-09-06 7:54 ` dkwo
2020-09-06 7:58 ` dkwo
2020-09-06 8:09 ` dkwo
2020-09-06 8:13 ` dkwo
2020-09-06 9:19 ` dkwo
2020-09-09 9:28 ` leahneukirchen
2020-09-09 11:28 ` dkwo
2020-09-15 6:57 ` dkwo
2020-09-15 6:59 ` dkwo
2020-09-15 7:00 ` dkwo
2020-09-15 7:00 ` dkwo
2020-09-15 11:49 ` dkwo
2020-09-15 12:35 ` dkwo
2020-10-12 15:57 ` dkwo
2020-12-30 15:29 ` dkwo
2021-02-11 11:11 ` dkwo
2021-02-11 11:12 ` dkwo
2021-02-24 9:59 ` dkwo
2021-02-24 10:03 ` dkwo
2021-02-24 10:03 ` dkwo
2021-02-24 12:25 ` tornaria
2021-02-24 13:50 ` dkwo
2021-02-24 13:50 ` dkwo
2021-03-15 9:11 ` dkwo
2021-03-15 9:11 ` dkwo
2021-03-15 9:11 ` dkwo
2021-03-18 15:24 ` dkwo
2021-03-20 17:43 ` dkwo
2021-03-20 17:44 ` dkwo
2021-08-20 6:52 ` Eloitor
2021-08-20 6:52 ` Eloitor
2021-08-20 8:59 ` dkwo
2021-08-20 8:59 ` dkwo
2021-08-20 9:04 ` dkwo
2021-08-20 9:04 ` dkwo
2021-08-20 9:06 ` dkwo
2021-08-20 9:07 ` dkwo
2021-08-20 12:06 ` tornaria [this message]
2021-08-23 8:41 ` dkwo
2021-08-23 16:47 ` dkwo
2021-08-23 17:01 ` tornaria
2021-08-25 9:46 ` dkwo
2021-08-27 9:11 ` dkwo
2021-08-29 11:20 ` dkwo
2021-08-29 13:03 ` tornaria
2021-08-29 18:11 ` dkwo
2021-08-29 18:12 ` dkwo
2021-08-29 18:20 ` dkwo
2021-09-01 15:59 ` dkwo
2021-09-02 13:59 ` dkwo
2021-09-02 13:59 ` dkwo
2021-09-02 14:55 ` tornaria
2021-09-02 15:24 ` tornaria
2021-09-03 16:14 ` dkwo
2021-09-04 20:14 ` Eloitor
2021-09-04 20:47 ` tornaria
2021-09-04 21:32 ` Eloitor
2021-09-04 21:46 ` tornaria
2021-09-05 10:05 ` Eloitor
2021-09-05 10:05 ` Eloitor
2021-09-06 9:59 ` dkwo
2021-09-06 16:50 ` dkwo
2021-09-07 11:28 ` dkwo
2021-09-27 9:01 ` dkwo
2021-11-06 10:20 ` dkwo
2021-11-06 10:20 ` dkwo
2021-11-08 15:28 ` leahneukirchen
2021-11-08 17:16 ` dkwo
2021-11-08 17:16 ` dkwo
2021-11-08 17:16 ` dkwo
2021-11-08 17:16 ` dkwo
2021-11-08 17:17 ` dkwo
2021-11-09 10:53 ` dkwo
2021-11-09 12:51 ` tornaria
2021-11-09 15:26 ` dkwo
2021-11-09 15:26 ` dkwo
2021-11-09 15:32 ` leahneukirchen
2021-11-09 15:32 ` leahneukirchen
2021-11-09 15:49 ` dkwo
2021-11-09 15:52 ` dkwo
2021-11-10 8:59 ` dkwo
2021-11-10 8:59 ` dkwo
2021-11-10 8:59 ` dkwo
2021-11-10 9:00 ` dkwo
2021-11-10 9:05 ` dkwo
2021-11-10 13:54 ` dkwo
2021-11-10 14:04 ` dkwo
2021-11-10 18:45 ` dkwo
2021-11-10 18:45 ` dkwo
2021-11-10 19:58 ` tornaria
2021-11-10 20:27 ` leahneukirchen
2021-11-10 20:33 ` tornaria
2021-11-10 20:40 ` leahneukirchen
2021-11-10 21:13 ` leahneukirchen
2021-11-11 10:06 ` dkwo
2021-11-11 10:06 ` dkwo
2021-11-11 10:32 ` dkwo
2021-11-11 14:13 ` tornaria
2021-11-14 10:13 ` dkwo
2021-11-22 3:53 ` tornaria
2021-11-22 19:25 ` dkwo
2021-11-22 19:26 ` dkwo
2021-11-22 19:26 ` dkwo
2021-11-22 19:26 ` dkwo
2021-11-22 19:27 ` dkwo
2021-11-22 19:27 ` dkwo
2021-11-22 19:27 ` dkwo
2021-11-22 19:28 ` dkwo
2021-11-22 19:28 ` dkwo
2022-01-02 8:37 ` [ISSUE] [CLOSED] " dkwo
2022-01-02 8:37 ` dkwo
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=20210820120631.lhsjdEnETQvoD54w0MW8UxAyD_6jj5AP5Py6dKsAWKU@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).