From: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: [RFC] mc: cleanup, python3, adopt.
Date: Mon, 31 Oct 2022 03:15:09 +0100 [thread overview]
Message-ID: <20221031021509.JTCrAo_J_R6SeiCiHk-sdVFya43en95QbggW3T9Cuv0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38079@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 856 bytes --]
There's a closed pull request on the void-packages repository
[RFC] mc: cleanup, python3, adopt.
https://github.com/void-linux/void-packages/pull/38079
Description:
This PR splits off python-dependent backends into a subpackage. This is the approach used in other distros.
However, this only takes care of having python, it does not take into account more programs that may be needed (like the uc1451 backend needing the `vice` package). Most backends are just thin translation layers over an external tool, and some need perl. None of those dependencies are marked as such in the package, nor are they in other distros. What would be the best way to deal with that?
#### Testing the changes
- I tested the changes in this PR: **YES**
It is impossible to test the s3 backend without an AWS S3 account, but the patch is used in other distros.
next prev parent reply other threads:[~2022-10-31 2:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-15 5:57 [PR PATCH] " 0x5c
2022-07-17 6:26 ` 0x5c
2022-07-17 7:28 ` 0x5c
2022-07-17 9:02 ` 0x5c
2022-10-16 2:14 ` github-actions
2022-10-31 2:15 ` github-actions [this message]
2023-10-10 1:42 ` [PR PATCH] [Updated] " 0x5c
2023-10-10 1:45 ` 0x5c
2023-10-10 1:49 ` mc: update to 4.8.29, cleanup, adopt 0x5c
2023-10-10 1:51 ` [PR PATCH] [Merged]: " classabbyamp
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=20221031021509.JTCrAo_J_R6SeiCiHk-sdVFya43en95QbggW3T9Cuv0@z \
--to=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).