From: tornaria <tornaria@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: sagemath: update to 10.1.
Date: Thu, 24 Aug 2023 01:25:45 +0200 [thread overview]
Message-ID: <20230823232545.yXDubqNlXPMVKnWz4XBLRtQYxJIDkYHs6LqxiihB9Hs@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: 922 bytes --]
New comment by tornaria on void-packages repository
https://github.com/void-linux/void-packages/pull/45708#issuecomment-1690769830
Comment:
> Looks good to me, thanks. I won't be able to run tests on aarch64 for three more weeks. How about the old idea of splitting a devel subpkg, which depends on devel stuff?
Sure. How would that work? What would we gain? I imagine:
- we remove some packages from `sagemath` depends.
- we create a meta package `sagemath-devel` which depends on `sagemath` and on all the packages we removed from `sagemath` depends.
As a matter of fact, I don't see what would be the point of `sagemath-devel`. I mean, if it's possible to use `sagemath` without those depends, then they shouldn't be depends in the first place.
An important point is: how would we test that the "depends" line is correct (i.e. that we don't remove something that is needed, e.g., to pass the testsuite).
next prev parent reply other threads:[~2023-08-23 23:25 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 [this message]
2023-08-24 11:41 ` 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
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=20230823232545.yXDubqNlXPMVKnWz4XBLRtQYxJIDkYHs6LqxiihB9Hs@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).