From: pablomancera <pablomancera@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: i3status-rust: update to 0.32.2.
Date: Sat, 23 Sep 2023 01:28:45 +0200 [thread overview]
Message-ID: <20230922232845.nEUZW764Zjki59eRaopRk6KfAbmS_g5DHim8snrzYOk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46079@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 956 bytes --]
New comment by pablomancera on void-packages repository
https://github.com/void-linux/void-packages/pull/46079#issuecomment-1732124482
Comment:
The idea of the line
`env -i bash -c "source /etc/profile && cargo xtask generate-manpage"`
is that the void build servers (which I think are x86_64) generates the man page using the packages native to their architecture and bundle them in the package for every other architecture. It's the solution I came up with after the review I got at #44899 so every architecture can get the man pages. I'm not entirely sure it's the best though, but it worked in my tests (local building for x86_64 and cross building for aarch64). If there is a better way of doing this I would like to hear it.
On the other hand, if anyone wants to build the package on an architecture limited by the pandoc package, they can disable the docs build option and it'll be fine.
That's the reason I added a docs build option.
next prev parent reply other threads:[~2023-09-22 23:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-16 5:28 [PR PATCH] " pablomancera
2023-09-22 22:02 ` Duncaen
2023-09-22 22:05 ` [PR REVIEW] " classabbyamp
2023-09-22 22:50 ` pablomancera
2023-09-22 23:01 ` Duncaen
2023-09-22 23:04 ` Duncaen
2023-09-22 23:04 ` Duncaen
2023-09-22 23:28 ` pablomancera [this message]
2023-09-22 23:36 ` [PR PATCH] [Updated] " pablomancera
2023-11-14 19:12 ` [PR PATCH] [Closed]: " pablomancera
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=20230922232845.nEUZW764Zjki59eRaopRk6KfAbmS_g5DHim8snrzYOk@z \
--to=pablomancera@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).