From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: New package: dnsdist-1.6.0
Date: Sat, 31 Jul 2021 04:11:57 +0200 [thread overview]
Message-ID: <20210731021157.AeCqXiOGFBzvmOs_9mPzFrUG_4uz_HdblOcdJb2eTBs@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31932@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1416 bytes --]
There's a merged pull request on the void-packages repository
New package: dnsdist-1.6.0
https://github.com/void-linux/void-packages/pull/31932
Description:
<!-- Mark items with [x] where applicable -->
#### General
- [X] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)
#### Have the results of the proposed changes been tested?
- [X] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] I generally don't use the affected packages but briefly tested this PR
#### Does it build and run successfully?
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [X] I built this PR locally for my native architecture, (x86_64-musl)
- [X] I built this PR locally for these architectures (if supported. mark crossbuilds):
- [X] aarch64-musl
- [ ] armv7l
- [ ] armv6l-musl
This is my second attempt (first one was #28109 ). Sorry for being such a newb, this is my first attempt at xbps packaging. The original PR wanted to use the upstream .conf instead of my sample one, so I went with the upstream one this time. The reason I didn't use it originally was because it's entirely commented out, so it doesn't work out of the box. I wanted a better user experience by default.
prev parent reply other threads:[~2021-07-31 2:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-13 0:27 [PR PATCH] " jailbird777
2021-07-17 4:00 ` [PR REVIEW] " ericonr
2021-07-17 4:00 ` ericonr
2021-07-17 4:00 ` ericonr
2021-07-17 4:11 ` [PR PATCH] [Updated] " jailbird777
2021-07-17 4:21 ` jailbird777
2021-07-17 4:34 ` jailbird777
2021-07-17 4:34 ` [PR REVIEW] " jailbird777
2021-07-17 4:36 ` jailbird777
2021-07-18 21:09 ` ericonr
2021-07-27 0:12 ` [PR PATCH] [Updated] " jailbird777
2021-07-27 0:13 ` jailbird777
2021-07-27 3:44 ` [PR PATCH] [Updated] " ericonr
2021-07-27 14:45 ` [PR REVIEW] " ericonr
2021-07-30 1:18 ` [PR PATCH] [Updated] " jailbird777
2021-07-30 1:18 ` [PR REVIEW] " jailbird777
2021-07-31 2:11 ` ericonr [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=20210731021157.AeCqXiOGFBzvmOs_9mPzFrUG_4uz_HdblOcdJb2eTBs@z \
--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).