From: HiPhish <HiPhish@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: (help needed) New package: sbcl-doc-2.1.11
Date: Tue, 28 Dec 2021 15:13:55 +0100 [thread overview]
Message-ID: <20211228141355.MHWKqgAkm16lvLo5yVN5uIR2NbetdIg7nb_ktJLPF40@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34730@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 771 bytes --]
New comment by HiPhish on void-packages repository
https://github.com/void-linux/void-packages/pull/34730#issuecomment-1002125622
Comment:
I think I have solved the issue, at least in a hacky way. Everything (including manuals) gets built, but then I move all the Info manual files into a separate directory. That way they won't get picked up by the installer script. In the `sbcl-doc` subpackage I manually copy the Info files over from the custom directory instead. If anyone has a better idea let me know, but that's the least hacky way I could think of. One downside though: the Info files do not get compressed automatically by XBPS.
Alternatively we could just ship the manual as part of the main package, that would be one like of code in the build function.
next prev parent reply other threads:[~2021-12-28 14:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-28 9:48 [PR PATCH] " HiPhish
2021-12-28 14:09 ` [PR PATCH] [Updated] " HiPhish
2021-12-28 14:13 ` HiPhish [this message]
2021-12-28 20:35 ` Chocimier
2021-12-28 20:36 ` Chocimier
2021-12-28 23:01 ` [PR PATCH] [Updated] " HiPhish
2021-12-28 23:13 ` HiPhish
2021-12-29 23:49 ` Chocimier
2021-12-30 12:04 ` [PR PATCH] [Updated] " HiPhish
2021-12-30 12:06 ` HiPhish
2021-12-30 14:08 ` leahneukirchen
2021-12-30 14:09 ` leahneukirchen
2021-12-30 15:44 ` [PR PATCH] [Updated] " HiPhish
2021-12-30 15:45 ` HiPhish
2021-12-30 15:46 ` HiPhish
2022-01-09 15:19 ` [PR PATCH] [Updated] " HiPhish
2022-01-09 15:19 ` HiPhish
2022-01-09 15:27 ` [PR PATCH] [Merged]: " leahneukirchen
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=20211228141355.MHWKqgAkm16lvLo5yVN5uIR2NbetdIg7nb_ktJLPF40@z \
--to=hiphish@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).