Github messages for voidlinux
 help / color / mirror / Atom feed
From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: [RFC] xtools: add xtools-minimal subpackage
Date: Thu, 07 Jul 2022 18:01:10 +0200	[thread overview]
Message-ID: <20220707160110.AKAo4Tm2_Cb3JsfGU6QcjfkTAU_qaceHO0KxCgLW2Lo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37826@inbox.vuxu.org>

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

There's a merged pull request on the void-packages repository

[RFC] xtools: add xtools-minimal subpackage
https://github.com/void-linux/void-packages/pull/37826

Description:
<!-- Uncomment relevant sections and delete options which are not applicable -->

#### Testing the changes
- I tested the changes in this PR: **YES**

- Not too sure about this approach, it's a bit clunky, and leaves non-included tools in the manpage.
- Should the subpackage be named as such or something else?
- is this list of tools a good selection? I took all the ones that aren't related to packaging *and* don't need git (the largest dependency by far)

see also:
- void-linux/void-mklive#255
- void-linux/void-docs#688

      parent reply	other threads:[~2022-07-07 16:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-04  1:23 [PR PATCH] [RFC] xtools: add xtools-live subpackage classabbyamp
2022-07-04 13:12 ` leahneukirchen
2022-07-04 16:02 ` [PR PATCH] [Updated] " classabbyamp
2022-07-04 16:06 ` classabbyamp
2022-07-04 17:26 ` [PR PATCH] [Updated] [RFC] xtools: add xtools-minimal subpackage classabbyamp
2022-07-07 16:01 ` classabbyamp [this message]

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=20220707160110.AKAo4Tm2_Cb3JsfGU6QcjfkTAU_qaceHO0KxCgLW2Lo@z \
    --to=classabbyamp@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).