From: 0x5c <0x5c@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: mc: update to 4.8.29, cleanup, adopt.
Date: Tue, 10 Oct 2023 03:49:07 +0200 [thread overview]
Message-ID: <20231010014907.9ULMg1qLtnrGyoYx6voTt1pH-Kd3QKBLA0PehhiRqLQ@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: 948 bytes --]
New comment by 0x5c on void-packages repository
https://github.com/void-linux/void-packages/pull/38079#issuecomment-1186429613
Comment:
I can see a couple of groupings that may be useful for defining subpackages
- APT/DPKG stuff: `apt+`, `deb`, `deba`, `debd`, `dpkg+` (how the hell is there 5 of them?)
- RPM stuff: `rpm`, `rpms+`, `trpm`
- things we don't have all the bits for: `bpp`, `hp48+`, `uace`, `ualz`, `uarc`, `uarj`, `uha`, `ulha`, `uzoo` (ARC here *might* be the same format as what PKARC was for?)
- git-related backends: `gitfs+`, `changesetfs`, `patchsetfs`
- misc, shared-depends backends: `mailfs`, `patchfs`, `lslR`
- archive file formats: `u7z`, `uar`, `ulib`, `unar`, `urar`, `ucab`, `uzip`
- disk/etc image formats: `iso9660`, `uc1541`, `uwim`
- hard to categorise backends: `a+`, `audio`, `s3+`
**EDIT:** This approach got dropped in favour of simply documenting what packages are needed for the extfs scripts
next prev parent reply other threads:[~2023-10-10 1:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-15 5:57 [PR PATCH] [RFC] mc: cleanup, python3, adopt 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 ` [PR PATCH] [Closed]: " github-actions
2023-10-10 1:42 ` [PR PATCH] [Updated] " 0x5c
2023-10-10 1:45 ` 0x5c
2023-10-10 1:49 ` 0x5c [this message]
2023-10-10 1:51 ` [PR PATCH] [Merged]: mc: update to 4.8.29, cleanup, adopt 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=20231010014907.9ULMg1qLtnrGyoYx6voTt1pH-Kd3QKBLA0PehhiRqLQ@z \
--to=0x5c@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).