From: tornaria <tornaria@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: lrcalc: update to 2.1, rebuild sagemath-9.5
Date: Fri, 18 Mar 2022 22:35:38 +0100 [thread overview]
Message-ID: <20220318213538.ds7JyjKU26s7p9ql9sTNSx2zukKuy0PTaRHhJNu-FaY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36209@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 938 bytes --]
New comment by tornaria on void-packages repository
https://github.com/void-linux/void-packages/pull/36209#issuecomment-1072834030
Comment:
> depends+="eclib-devel flintlib-devel gcc-fortran gd-devel gsl-devel libpng-devel linbox-devel m4ri-devel mpfr-devel ntl-devel pari-devel python3-devel"
Granted, there are some large packages there. I'd like to have a look at what extent these are used in sage, etc. Ideally there should be a feature flag that indicates that a doctest only works when a working C compiler is installed, etc. That needs to be done with upstream.
What would happen to doctesting in CI? I guess that would still work since it's done in the masterdir...
Let me think about it... We need some good workflow to play with bare-bones void so we can test dependencies are ok, because an xbps-src chroot always contain gcc, etc. which will may not be installed (gcc is pulled in as a dependency of gcc-fortran).
next prev parent reply other threads:[~2022-03-18 21:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-18 18:29 [PR PATCH] " tornaria
2022-03-18 19:45 ` dkwo
2022-03-18 20:24 ` tornaria
2022-03-18 20:41 ` dkwo
2022-03-18 21:08 ` [PR PATCH] [Updated] " tornaria
2022-03-18 21:35 ` tornaria [this message]
2022-03-19 8:14 ` dkwo
2022-04-04 1:31 ` tornaria
2022-04-04 1:31 ` [PR PATCH] [Closed]: " tornaria
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=20220318213538.ds7JyjKU26s7p9ql9sTNSx2zukKuy0PTaRHhJNu-FaY@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).