From: tornaria <tornaria@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [RFC] New package: sagelib-9.5
Date: Tue, 01 Feb 2022 13:17:05 +0100 [thread overview]
Message-ID: <20220201121705.Lv7OPxpeMra5qOX7Qt1VuVOsUTO9kvs7VIJP9KLOe2k@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35339@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1007 bytes --]
New comment by tornaria on void-packages repository
https://github.com/void-linux/void-packages/pull/35339#issuecomment-1026782273
Comment:
> Let me first say you've done a great job. I'm building it right now, will report soon. My only comment is about `depends`: is there a way not to bring in `-devel` and `gcc-` stuff?
I only added stuff that is needed to pass doctests. There is some functionality to cython-compile code (e.g. you may want to define a function in cython inside a notebook) and that needs at least headers and sometimes libraries, and a working gcc (which is required indirectly via gcc-fortran).
It might be possible to add "features" to sage that correspond to presence of gcc and headers, etc. but I'm not sure this is worth the trouble. Although some sage developers are trying to move it in a "modularization" direction such that it's possible to split it in parts and in that sense it could make sense to split out a "sagemath-cython" subpkg that gives this ability, etc.
next prev parent reply other threads:[~2022-02-01 12:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-01 4:05 [PR PATCH] " tornaria
2022-02-01 9:21 ` dkwo
2022-02-01 10:10 ` dkwo
2022-02-01 10:12 ` dkwo
2022-02-01 10:13 ` dkwo
2022-02-01 12:17 ` tornaria [this message]
2022-02-01 12:58 ` tornaria
2022-02-01 13:32 ` dkwo
2022-02-01 13:32 ` dkwo
2022-02-01 13:32 ` tornaria
2022-02-01 13:32 ` dkwo
2022-02-01 13:39 ` dkwo
2022-02-01 13:55 ` dkwo
2022-02-01 15:14 ` leahneukirchen
2022-02-01 15:25 ` [PR PATCH] [Updated] " tornaria
2022-02-01 15:51 ` tornaria
2022-02-01 21:40 ` leahneukirchen
2022-02-02 21:06 ` tornaria
2022-02-02 21:06 ` [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=20220201121705.Lv7OPxpeMra5qOX7Qt1VuVOsUTO9kvs7VIJP9KLOe2k@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).