From: tornaria <tornaria@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [RFC] build-style/haskell-stack: place stack root in /host to make it persistent
Date: Tue, 26 Mar 2024 19:08:57 +0100 [thread overview]
Message-ID: <20240326180857.7DE2322736@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-49526@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 934 bytes --]
New comment by tornaria on void-packages repository
https://github.com/void-linux/void-packages/pull/49526#issuecomment-2021150796
Comment:
I think `STACK_ROOT` contains build artifacts. Not for the current package you are building, but only for all the dependencies taken from stackage. IOW, if you build pandoc again, it's source will be recompiled each time, but the dependencies will be built only the first time (for each architecture).
It also seems to contain the registry and downloaded sources, but it's not obvious to me how to share this between architectures while having binaries separate (especially x86_64 vs x86_64-musl which they are both named `x86_64-linux` for stack, but are not compatible).
This seems to be working ok, but I'll test a bit more. I do have pandoc update working on x86_64 but it's failing on musl (this was fixed before in #36292 but it's not obvious to me how to bring the fix forward).
prev parent reply other threads:[~2024-03-26 18:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-25 15:43 [PR PATCH] " tornaria
2024-03-25 19:58 ` classabbyamp
2024-03-25 23:53 ` [PR PATCH] [Updated] " tornaria
2024-03-26 0:29 ` [PR REVIEW] " sgn
2024-03-26 0:38 ` classabbyamp
2024-03-26 0:45 ` [PR PATCH] [Updated] " tornaria
2024-03-26 0:52 ` tornaria
2024-03-26 1:04 ` [PR PATCH] [Updated] " tornaria
2024-03-26 7:59 ` 0x5c
2024-03-26 18:08 ` tornaria [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=20240326180857.7DE2322736@inbox.vuxu.org \
--to=tornaria@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).