From: chexum <chexum@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: libguestfs-tools 1.48.0
Date: Wed, 29 Jun 2022 18:04:24 +0200 [thread overview]
Message-ID: <20220629160424.y22-sASPwIpPpybNcX3VIFqswk06cd1UoEKsv3u7dMM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37416@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 680 bytes --]
New comment by chexum on void-packages repository
https://github.com/void-linux/void-packages/pull/37416#issuecomment-1170175736
Comment:
> We generally use upstream names, anything wrong with using `guestfs-tools`?
Even the internal library common to `libguestfs` and `guestfs-tools` is residing in `libguestfs-common`. Perhaps the vendor name was chosen to only have a name that's shorter to type, but it's all still for the libguestfs family. Both the two major distributions use the name `libguestfs-tools` as well. This way it could reduce the confusion of both new users, to learn about the package, and users from other distributions, to find the package they know.
next prev parent reply other threads:[~2022-06-29 16:04 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-05 19:14 [PR PATCH] " chexum
2022-06-05 19:19 ` [PR PATCH] [Updated] " chexum
2022-06-09 5:17 ` chexum
2022-06-26 16:59 ` [PR PATCH] [Updated] New package: " chexum
2022-06-27 11:28 ` chexum
2022-06-27 22:22 ` Duncaen
2022-06-27 22:45 ` [PR REVIEW] " Duncaen
2022-06-27 22:46 ` Duncaen
2022-06-27 22:46 ` Duncaen
2022-06-27 22:48 ` Duncaen
2022-06-29 16:04 ` chexum [this message]
2022-06-29 16:27 ` chexum
2022-06-29 16:50 ` [PR PATCH] [Updated] " chexum
2022-06-29 16:51 ` [PR REVIEW] " chexum
2022-06-29 17:02 ` Duncaen
2022-07-03 14:51 ` chexum
2022-10-02 2:15 ` github-actions
2022-10-09 18:56 ` chexum
2023-01-09 1:58 ` github-actions
2023-01-18 18:09 ` chexum
2023-04-20 1:51 ` github-actions
2023-05-05 1:49 ` [PR PATCH] [Closed]: " 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=20220629160424.y22-sASPwIpPpybNcX3VIFqswk06cd1UoEKsv3u7dMM@z \
--to=chexum@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).