From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Math package: lcalc-1.23
Date: Wed, 07 Apr 2021 22:33:00 +0200 [thread overview]
Message-ID: <20210407203300.3Zq3iTWeZMhcg4eLps7s0MeQwvIT7twub0JFWdCKX90@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-30036@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1010 bytes --]
New comment by ericonr on void-packages repository
https://github.com/void-linux/void-packages/pull/30036#issuecomment-815242908
Comment:
> I could update it to have exactly the same patches as in sagemath (either included in or as distfiles from a stable tag of the git repo above) and think of sagemath as the upstream.
I think the distfiles approach here would be best. Any local patches would go on top of that, and we avoid vendoring in a bunch of "basic" patches.
> But when we get to package sagemath, this program will have to be compiled, either as a separate package (like here) or as part of the omnibus sagemath.
Alternatively, **I** am ok with it being packaged inside of sagemath; it is, after all, the only user for it, so there are very few (if any - maybe it helps with cross builds?) benefits from splitting it into a separate package. Other maintainers might have other opinions on vendoring dependencies, even in this case, so don't consider my opinion the final recommendation.
next prev parent reply other threads:[~2021-04-07 20:33 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-06 5:10 [PR PATCH] " tornaria
2021-04-06 5:21 ` [PR PATCH] [Updated] " tornaria
2021-04-07 12:56 ` dkwo
2021-04-07 17:54 ` [PR REVIEW] " Chocimier
2021-04-07 17:54 ` Chocimier
2021-04-07 17:56 ` ericonr
2021-04-07 18:01 ` ericonr
2021-04-07 20:11 ` tornaria
2021-04-07 20:16 ` tornaria
2021-04-07 20:33 ` ericonr [this message]
2021-04-07 20:49 ` tornaria
2021-04-07 21:26 ` ericonr
2021-04-07 22:10 ` [PR PATCH] [Updated] " tornaria
2021-04-07 22:16 ` tornaria
2021-04-07 22:24 ` tornaria
2021-04-08 0:46 ` [PR REVIEW] " ericonr
2021-04-08 0:46 ` ericonr
2021-04-08 0:46 ` ericonr
2021-04-08 0:46 ` ericonr
2021-04-08 0:47 ` ericonr
2021-04-08 1:06 ` [PR REVIEW] " tornaria
2021-04-08 1:06 ` tornaria
2021-04-08 1:08 ` [PR PATCH] [Updated] " tornaria
2021-04-08 1:16 ` [PR REVIEW] " tornaria
2021-04-08 1:20 ` [PR PATCH] [Updated] " tornaria
2021-04-08 1:49 ` tornaria
2021-04-08 2:03 ` ericonr
2021-04-08 3:08 ` [PR PATCH] [Updated] " tornaria
2021-04-08 3:13 ` tornaria
2021-04-09 2:26 ` [PR REVIEW] " ericonr
2021-04-09 2:41 ` [PR PATCH] [Updated] " tornaria
2021-04-09 2:43 ` tornaria
2021-04-09 2:45 ` [PR REVIEW] " tornaria
2021-04-09 2:46 ` tornaria
2021-04-09 17:22 ` Chocimier
2021-08-18 22:37 ` [PR PATCH] [Updated] " tornaria
2021-08-19 1:42 ` tornaria
2021-10-31 9:01 ` dkwo
2021-11-03 20:50 ` [PR PATCH] [Merged]: " Chocimier
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=20210407203300.3Zq3iTWeZMhcg4eLps7s0MeQwvIT7twub0JFWdCKX90@z \
--to=ericonr@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).