From: tornaria <tornaria@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: sagemath: update to 10.1.
Date: Sat, 26 Aug 2023 21:29:47 +0200 [thread overview]
Message-ID: <20230826192947.TJrVrY10lyiapC1odOduiFeVHi9cQXwlbsN97rDPBDk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45708@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 888 bytes --]
New comment by tornaria on void-packages repository
https://github.com/void-linux/void-packages/pull/45708#issuecomment-1694487072
Comment:
> We could remove
>
> ```
> depends+=" eclib-devel flintlib-devel gcc-fortran gd-devel
> gsl-devel libpng-devel linbox-devel m4ri-devel
> mpfr-devel ntl-devel pari-devel pkg-config python3-devel"
> ```
>
> and then see which tests fail from within installed sage; within the build chroot, there should be no difference, as those packages are already in (host)makedepends. Does that make sense?
Nothing will fail inside the build chroot, since as you said, these are already installed via (host)makedepends. That's precisely the issue I am worried about.
The only easy way I see is to have a separate meta package to test sagemath, with a checkdepends on sagemath, which runs the sagemath testsuite (on the installed package).
next prev parent reply other threads:[~2023-08-26 19:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-21 23:17 [PR PATCH] " tornaria
2023-08-22 14:46 ` tornaria
2023-08-22 16:47 ` [PR PATCH] [Updated] " tornaria
2023-08-22 21:00 ` tornaria
2023-08-23 17:32 ` dkwo
2023-08-23 23:06 ` [PR PATCH] [Updated] " tornaria
2023-08-23 23:25 ` tornaria
2023-08-24 11:41 ` [PR PATCH] [Updated] " tornaria
2023-08-26 15:50 ` dkwo
2023-08-26 19:29 ` tornaria [this message]
2023-08-28 2:57 ` tornaria
2023-08-28 19:05 ` [PR PATCH] [Updated] " tornaria
2023-08-28 19:10 ` tornaria
2023-08-29 13:06 ` tornaria
2023-08-30 20:39 ` tornaria
2023-08-30 21:35 ` tornaria
2023-08-31 0:52 ` tornaria
2023-08-31 7:00 ` dkwo
2023-08-31 11:57 ` [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=20230826192947.TJrVrY10lyiapC1odOduiFeVHi9cQXwlbsN97rDPBDk@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).