From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: wlroots: update to 0.16, labwc: update to 0.6.0
Date: Fri, 18 Nov 2022 13:13:04 +0100 [thread overview]
Message-ID: <20221118121304.e2_pTra5dxKPctK-EfV8eNGlDCsCdxQfdiH20kD98VM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40587@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 789 bytes --]
New comment by paper42 on void-packages repository
https://github.com/void-linux/void-packages/pull/40587#issuecomment-1319919346
Comment:
> > The current plan is to finish the gcc update to 12 and then package LLVM 15, then zig 0.9 and then we can update river. We are working on this, but this can take a while.
>
> Zig 0.9 requires exactly llvm 13 actually, but I intend for the next river release to depend on Zig 0.10 which depends on LLVM 15 so this shouldn't be an issue. Just leaving this comment here for clarity, the overall plan of action seems reasonable to me.
I am aware of that, but updating LLVM is a non-trivial task, so we will probably go straight to the latest available version and skip 13 and 14 which means an LLVM update has to happen after the gcc update.
next prev parent reply other threads:[~2022-11-18 12:13 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-18 1:15 [PR PATCH] " tranzystorek-io
2022-11-18 1:16 ` tranzystorek-io
2022-11-18 1:30 ` [PR REVIEW] " paper42
2022-11-18 1:40 ` tranzystorek-io
2022-11-18 1:47 ` [PR PATCH] [Updated] " tranzystorek-io
2022-11-18 2:00 ` tranzystorek-io
2022-11-18 2:56 ` cinerea0
2022-11-18 6:19 ` tranzystorek-io
2022-11-18 10:27 ` [PR PATCH] [Updated] " tranzystorek-io
2022-11-18 10:44 ` paper42
2022-11-18 10:54 ` [PR PATCH] [Updated] wlroots: update to 0.16, " tranzystorek-io
2022-11-18 11:08 ` tranzystorek-io
2022-11-18 12:05 ` ifreund
2022-11-18 12:07 ` tranzystorek-io
2022-11-18 12:13 ` paper42 [this message]
2022-11-26 18:55 ` [PR PATCH] [Updated] " tranzystorek-io
2022-11-27 0:45 ` [PR REVIEW] " paper42
2022-11-27 8:53 ` [PR PATCH] [Updated] " tranzystorek-io
2022-11-27 8:57 ` [PR REVIEW] " tranzystorek-io
2022-11-27 16:35 ` paper42
2022-11-27 16:35 ` paper42
2022-11-27 19:38 ` tranzystorek-io
2022-11-28 17:13 ` [PR PATCH] [Updated] " tranzystorek-io
2022-11-28 17:14 ` tranzystorek-io
2022-11-28 17:14 ` [PR REVIEW] " tranzystorek-io
2022-11-28 17:42 ` paper42
2022-11-28 17:42 ` paper42
2022-11-28 17:42 ` paper42
2022-11-28 17:42 ` paper42
2022-11-28 17:56 ` [PR PATCH] [Updated] " tranzystorek-io
2022-11-28 17:57 ` [PR REVIEW] " tranzystorek-io
2022-11-28 17:57 ` tranzystorek-io
2022-11-28 17:58 ` tranzystorek-io
2022-11-28 18:08 ` [PR PATCH] [Updated] " tranzystorek-io
2022-11-29 18:16 ` skmpz
2022-12-03 12:49 ` [PR REVIEW] " ardadem
2022-12-06 7:16 ` [PR PATCH] [Updated] " tranzystorek-io
2022-12-06 7:31 ` tranzystorek-io
2022-12-06 8:50 ` [PR REVIEW] " paper42
2022-12-06 10:18 ` [PR PATCH] [Updated] " tranzystorek-io
2022-12-06 10:29 ` tranzystorek-io
2022-12-06 10:45 ` tranzystorek-io
2022-12-06 11:01 ` [PR REVIEW] " tranzystorek-io
2022-12-27 10:22 ` [PR PATCH] [Updated] " tranzystorek-io
2022-12-27 10:40 ` tranzystorek-io
2022-12-27 10:41 ` [PR REVIEW] " tranzystorek-io
2022-12-27 17:32 ` paper42
2022-12-27 17:33 ` paper42
2022-12-27 19:07 ` [PR PATCH] [Updated] " tranzystorek-io
2022-12-27 19:08 ` [PR REVIEW] " tranzystorek-io
2022-12-27 19:08 ` tranzystorek-io
2022-12-27 22:21 ` [PR PATCH] [Merged]: " paper42
2022-12-29 0:54 ` [PR REVIEW] " mhmdanas
2022-12-29 8:39 ` tranzystorek-io
2022-12-29 8:40 ` tranzystorek-io
2022-12-29 14:48 ` mhmdanas
2022-12-30 3:18 ` mhmdanas
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=20221118121304.e2_pTra5dxKPctK-EfV8eNGlDCsCdxQfdiH20kD98VM@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).