From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] [RFC] Add a tools directory?
Date: Mon, 01 Feb 2021 01:39:17 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28371@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1027 bytes --]
New issue by ericonr on void-packages repository
https://github.com/void-linux/void-packages/issues/28371
Description:
While maintaining void-packages, a lot of people have written small tools/scripts to help with simple tasks. There is a part of `xtools`, for example, that's only useful inside void-packages (unlike, for example, `xi` or `xls`).
I'm proposing a `tools/` directory to which we could move some of xtools (moving `xlint` to void-packages has even been discussed a few times, since it'd make it possible to add new variables to templates in a single go; `xrevbump` and `xsubpkg` are also not very useful outside of void-packages).
Further, there are small scripts like @Johnnynator's one for handling git submodules, @Chocimier's for detecting cycles in dependencies and @Piraty's for launching multiple builds at the same time. I'd also put forward the one I have to check what I have installed from packages listed in void-updates, so I have an idea of what I can easily test.
Ping @leahneukirchen
next reply other threads:[~2021-02-01 0:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-01 0:39 ericonr [this message]
2021-02-01 13:01 ` leahneukirchen
2021-03-05 6:08 ` ahesford
2021-08-12 23:03 ` fosslinux
2021-08-13 1:23 ` ericonr
2021-08-13 1:23 ` [ISSUE] [CLOSED] " ericonr
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28371@inbox.vuxu.org \
--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).