From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: nsxiv-27.1
Date: Tue, 21 Sep 2021 09:16:28 +0200 [thread overview]
Message-ID: <20210921071628.HMrP8dJMouc5_8_D7E1HMJipAgfJDMjEsL43URgW47k@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33009@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 861 bytes --]
New comment by paper42 on void-packages repository
https://github.com/void-linux/void-packages/pull/33009#issuecomment-923699397
Comment:
> Does anyone have any idea why merging this pull request takes so long?
New packages need to be properly reviewed and maintainers need to be at least a bit interested in maintaining the package, fixing it when the build breaks or dropping it if the original maintainer goes away. In this case it's simpler because it this is a simple program. If this was just an upstream change for sxiv, it would be simpler to review, but this is a fork which changes the project name, so it needs to be a new package.
I noticed this package installs examples in /usr/share/nsxiv/exec/, but sxiv installs them in /usr/share/examples. Do you know why this change was made? Do you think we should move them to /usr/share/examples?
next prev parent reply other threads:[~2021-09-21 7:16 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-18 6:23 [PR PATCH] " WitherCubes
2021-09-21 1:29 ` WitherCubes
2021-09-21 7:05 ` paper42
2021-09-21 7:06 ` paper42
2021-09-21 7:16 ` paper42 [this message]
2021-09-21 11:41 ` WitherCubes
2021-09-21 18:00 ` [PR REVIEW] " Johnnynator
2021-09-21 19:46 ` N-R-K
2021-09-21 19:53 ` paper42
2021-09-21 20:00 ` N-R-K
2021-09-21 20:04 ` paper42
2021-09-21 20:09 ` N-R-K
2021-09-21 20:09 ` N-R-K
2021-09-21 22:22 ` eylles
2021-09-21 23:08 ` N-R-K
2021-09-22 11:58 ` [PR PATCH] [Updated] " WitherCubes
2021-09-22 12:00 ` WitherCubes
2021-09-22 20:27 ` N-R-K
2021-09-24 14:54 ` [PR PATCH] [Updated] " WitherCubes
2021-09-24 14:56 ` [PR REVIEW] " WitherCubes
2021-09-24 15:27 ` paper42
2021-09-24 15:42 ` WitherCubes
2021-09-24 15:43 ` WitherCubes
2021-09-24 15:49 ` [PR PATCH] [Updated] " WitherCubes
2021-09-24 15:53 ` WitherCubes
2021-09-24 16:04 ` WitherCubes
2021-09-24 16:07 ` WitherCubes
2021-09-25 15:01 ` [PR REVIEW] " paper42
2021-09-25 16:34 ` [PR PATCH] [Updated] " WitherCubes
2021-09-25 16:53 ` WitherCubes
2021-09-25 17:06 ` [PR PATCH] [Updated] " WitherCubes
2021-09-25 17:07 ` WitherCubes
2021-09-25 17:28 ` [PR PATCH] [Updated] " WitherCubes
2021-09-28 9:44 ` [PR PATCH] [Merged]: " paper42
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=20210921071628.HMrP8dJMouc5_8_D7E1HMJipAgfJDMjEsL43URgW47k@z \
--to=paper42@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).