Github messages for voidlinux
 help / color / mirror / Atom feed
From: tornaria <tornaria@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: ecl: update to 23.9.9.
Date: Mon, 11 Sep 2023 18:07:17 +0200	[thread overview]
Message-ID: <20230911160717.g-6PxnKpRYCdlLmGt7qbKYR3MJipbT16TjTDstKuIwU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46003@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1186 bytes --]

New comment by tornaria on void-packages repository

https://github.com/void-linux/void-packages/pull/46003#issuecomment-1714183881

Comment:
Thanks for your quick answer!

> I'm not sure what's expected from package maintainers. If there is a clear expectation, I can try to meet it, as I still do want to contribute and may have more time upcoming.

I'm not sure either. I guess keep packages up to date when necessary, fix when there is breakage, etc. I think its quite useful that the maintainer is a frequent user of the package.

> I'm also ok with orphaning the packages if that will benefit the project, or if this package is particularly important to you, I can pass maintainership to you.

Only reason is because it is a core dependency of sagemath and maxima, but I'm not too much into lisp myself. I usually monitor some packages of interest like `ecl` and I don't mind doing updates and pinging you for feedback as here.

If you are a regular user of `ecl` you are definitely a better maintainer than me (I only use it indirectly via sagemath -> maxima -> ecl, and not a lot since I'm not a big user of symbolics in sagemath, which is the part that uses maxima).

  parent reply	other threads:[~2023-09-11 16:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-10 15:09 [PR PATCH] " tornaria
2023-09-10 22:56 ` tornaria
2023-09-11  5:19 ` knusbaum
2023-09-11 16:07 ` tornaria [this message]
2023-09-19 19:27 ` [PR PATCH] [Updated] " tornaria
2023-09-22  0:38 ` tornaria
2023-09-22 22:06 ` [PR PATCH] [Merged]: " Duncaen

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=20230911160717.g-6PxnKpRYCdlLmGt7qbKYR3MJipbT16TjTDstKuIwU@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).