From: oreo639 <oreo639@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: glib: update to 2.80.0.
Date: Wed, 17 Apr 2024 04:44:53 +0200 [thread overview]
Message-ID: <20240417024453.96BAA21757@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-49446@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 454 bytes --]
New comment by oreo639 on void-packages repository
https://github.com/void-linux/void-packages/pull/49446#issuecomment-2060239705
Comment:
Should be basically done.
I removed `${makedepends}` from the depends of libglib-devel, not sure why it is there in the first place but glib shouldn't include other headers. This may break some stuff that expects those devel packages to get implicitly pulled in though. I'm going to test building some packages.
next prev parent reply other threads:[~2024-04-17 2:44 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-21 20:10 [PR PATCH] " oreo639
2024-03-21 20:22 ` [PR PATCH] [Updated] [WIP] " oreo639
2024-03-21 20:23 ` oreo639
2024-03-21 20:50 ` oreo639
2024-03-21 21:04 ` oreo639
2024-03-21 21:08 ` chrysos349
2024-03-21 21:16 ` oreo639
2024-03-21 21:18 ` oreo639
2024-03-21 21:24 ` [PR PATCH] [Updated] " oreo639
2024-03-21 21:31 ` oreo639
2024-03-22 0:15 ` oreo639
2024-03-22 0:48 ` oreo639
2024-03-22 7:29 ` oreo639
2024-03-22 7:58 ` oreo639
2024-03-22 7:58 ` oreo639
2024-03-22 8:00 ` oreo639
2024-03-22 8:03 ` oreo639
2024-03-22 8:19 ` oreo639
2024-03-22 8:20 ` oreo639
2024-03-22 8:20 ` oreo639
2024-03-22 8:20 ` oreo639
2024-03-22 8:22 ` oreo639
2024-03-22 23:13 ` [PR PATCH] [Updated] " oreo639
2024-03-23 0:09 ` oreo639
2024-03-23 0:12 ` [PR PATCH] [Updated] " oreo639
2024-03-23 0:14 ` oreo639
2024-03-24 9:14 ` oreo639
2024-04-14 8:38 ` [PR PATCH] [Updated] " oreo639
2024-04-14 21:44 ` oreo639
2024-04-17 2:23 ` oreo639
2024-04-17 2:32 ` oreo639
2024-04-17 2:37 ` oreo639
2024-04-17 2:40 ` [PR PATCH] [Updated] " oreo639
2024-04-17 2:44 ` oreo639 [this message]
2024-04-17 2:46 ` oreo639
2024-04-17 2:53 ` [PR PATCH] [Updated] " oreo639
2024-04-17 2:53 ` oreo639
2024-04-17 3:21 ` oreo639
2024-04-17 3:36 ` oreo639
2024-04-17 3:47 ` [PR PATCH] [Updated] " oreo639
2024-04-17 3:49 ` oreo639
2024-04-17 23:36 ` oreo639
2024-04-18 0:28 ` oreo639
2024-04-18 3:02 ` oreo639
2024-04-18 3:25 ` [PR PATCH] [Merged]: " oreo639
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=20240417024453.96BAA21757@inbox.vuxu.org \
--to=oreo639@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).