From: tornaria <tornaria@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: sagemath: update to 10.1.
Date: Wed, 30 Aug 2023 23:35:15 +0200 [thread overview]
Message-ID: <20230830213515.1RZ5JGd26SNtYbZb_JfjnB4X3GBeA1fGtArJsslPfZ0@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: 1352 bytes --]
New comment by tornaria on void-packages repository
https://github.com/void-linux/void-packages/pull/45708#issuecomment-1699877312
Comment:
> @dkwo all dependencies you singled out are needed to use either cython or fortran in sagemath, which are not optional (at least the testsuite fails without them).
>
> I can imagine both features to be made optional, but I'm wary, something needs to happen so these are made optional and the testsuite works fine (a "feature" is detected, etc).
>
> What is the need / advantage of this? I guess some download or installed size, but how much? Is it really worth it?
I think this will become possible soon, but not yet. The sagemath doctests are adding "feature flags" which detect features in the environment, but this is not yet completely polished for cython / external libraries / fortran code.
At this time, I'd rather focus on getting sagemath working on cython 3 so we can update cython (see #45086 and https://github.com/ahesford/void-packages/pull/2). After 10.2 or 10.3 it may be easier to do this.
In any case, I'd like to see a detail of how much is saved (say how much download/disk it takes now an install of sagemath with all deps not standard in void vs. what would it take if we get this "savings"). If the savings is not really very significant, I'm not sure I see the point...
next prev parent reply other threads:[~2023-08-30 21:35 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
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 [this message]
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=20230830213515.1RZ5JGd26SNtYbZb_JfjnB4X3GBeA1fGtArJsslPfZ0@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).