From: leahneukirchen <leahneukirchen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: inspircd: update to 3.13.0.
Date: Fri, 29 Apr 2022 17:57:31 +0200 [thread overview]
Message-ID: <20220429155731.NHsVR4kXBiXum9x8QVVa4Pn6Nf_YkZY2aiL7fQLv2BI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36911@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1425 bytes --]
There's a merged pull request on the void-packages repository
inspircd: update to 3.13.0.
https://github.com/void-linux/void-packages/pull/36911
Description:
#### Testing the changes
- I tested the changes in this PR: **YES**
#### Local build testing
- I built this PR locally for my native architecture, x86-64
---
This updates InspIRCd to v3.13.0 and fixes the following package problems:
- Fixed depending on geoip-devel instead of libmaxminddb-devel. This is a leftover from v2.
- Fixed not passing `--disable-auto-extras` to configure. Without this the previous call to `--enable-extras` would have been overridden and resulted in the enabled extra modules being based on what is installed on the build system.
- Fixed not explicitly enabling modules that would have otherwise been automatically enabled based on the dependent packages.
- Fixed using `--gid 0 --uid 0` instead of `--disable-ownership`. The latter is more appropriate for distribution packages.
- Fixed manually specifying directories in configure instead of using `--system`. Other than `--binary-dir` all of the directories specified were the default for a system-wide install anyway. This also fixes files being installed into /usr.
[Note: I am the upstream for this software but I am not a Void user. I have nonetheless tested in a VM to the best of my abilities. Thanks to @leahneukirchen for the help with this.]
prev parent reply other threads:[~2022-04-29 15:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-29 14:58 [PR PATCH] " SadieCat
2022-04-29 15:57 ` leahneukirchen [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=20220429155731.NHsVR4kXBiXum9x8QVVa4Pn6Nf_YkZY2aiL7fQLv2BI@z \
--to=leahneukirchen@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).