From: ArsenArsen <ArsenArsen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [NOMERGE] glibc: generate gconv cache when possible
Date: Tue, 24 Aug 2021 20:14:51 +0200 [thread overview]
Message-ID: <20210824181451.tqpfuNK2dTl1bKbnyxI0s4nWBzYm1OHBRszjncMfSfA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29103@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 876 bytes --]
New comment by ArsenArsen on void-packages repository
https://github.com/void-linux/void-packages/pull/29103#issuecomment-904867076
Comment:
Now that the issue that was blocking this is resolved, we can continue to re-evaluate this PR.
Right now, the install appears to work, including a force reinstall, which means that the old problem is gone, now what's left to decide is whether to figure out building this cache ahead of time, on the build server. According to my recollection, there's no specified format for this file, so the host libcs and target libcs caches may differ, but I can consult developers of other distributions for advice with this, maybe that's only the case theoretically, and in practice the format hasn't changed, ever? Maybe it fails gracefully if the file is wrong?
Is the ABI problem even an issue now that INSTALL scripts are batched up?
next prev parent reply other threads:[~2021-08-24 18:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-27 21:57 [PR PATCH] glibc: add INSTALL hook to make gconv module cache ArsenArsen
2021-02-27 21:58 ` [PR REVIEW] " ericonr
2021-02-27 22:12 ` [PR PATCH] [Updated] " ArsenArsen
2021-02-27 22:34 ` ArsenArsen
2021-02-27 22:36 ` ArsenArsen
2021-02-27 22:55 ` [PR REVIEW] " ericonr
2021-02-27 23:07 ` [PR PATCH] [Updated] " ArsenArsen
2021-02-28 7:10 ` ericonr
2021-02-28 19:11 ` ArsenArsen
2021-02-28 19:32 ` Duncaen
2021-02-28 20:44 ` ArsenArsen
2021-02-28 23:54 ` [PR PATCH] [Updated] " ArsenArsen
2021-03-02 7:07 ` [PR PATCH] [Updated] glibc: generate gconv cache when possible ArsenArsen
2021-03-04 18:02 ` ArsenArsen
2021-03-06 12:21 ` [PR PATCH] [Updated] " ArsenArsen
2021-08-24 18:11 ` [PR PATCH] [Updated] [NOMERGE] " ArsenArsen
2021-08-24 18:14 ` ArsenArsen [this message]
2022-05-05 2:09 ` github-actions
2022-05-19 2:15 ` [PR PATCH] [Closed]: " github-actions
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=20210824181451.tqpfuNK2dTl1bKbnyxI0s4nWBzYm1OHBRszjncMfSfA@z \
--to=arsenarsen@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).