From: Duncaen <Duncaen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Undocumented xbps-src commands
Date: Wed, 10 Mar 2021 22:50:07 +0100 [thread overview]
Message-ID: <20210310215007.5X9w6IeYvYizH3o-9g0CDJkcRwnRH-vRWOQG7KuQZAs@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29363@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 587 bytes --]
New comment by Duncaen on void-packages repository
https://github.com/void-linux/void-packages/issues/29363#issuecomment-796180350
Comment:
I don't think each of those commands need to be documented in the help/usage, its already pretty big and there is no point in knowing `dbulk-dump` from a users perspective who is not trying to build tooling around xbps-src.
Same goes for the `show-pkg-var` they do the same thing as `dbulk-dump` but with a "looser" output format.
`remove-destdir` looks like just an alias for `remove`, I don't see the harm in keeping it for compatibility.
next parent reply other threads:[~2021-03-10 21:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29363@inbox.vuxu.org>
2021-03-10 21:50 ` Duncaen [this message]
2021-03-10 23:57 ` ericonr
2022-05-07 2:06 ` github-actions
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=20210310215007.5X9w6IeYvYizH3o-9g0CDJkcRwnRH-vRWOQG7KuQZAs@z \
--to=duncaen@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).