From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: Bibletime 3.0
Date: Sat, 12 Dec 2020 07:50:46 +0100 [thread overview]
Message-ID: <20201212065046.mJUPUAxHAF56lH1LzWSZuXZRxd5gEOaazmsexgC7_Wo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-26780@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1162 bytes --]
There's a merged pull request on the void-packages repository
Bibletime 3.0
https://github.com/void-linux/void-packages/pull/26780
Description:
The apache-fop commit has been included here because it is required to get bibletime to build one of the PDFs. I believe this is an acceptable change instead of changing fop.conf for bibletime because the PDFs are not very long or complex, so it would be common for people to need to change it anyway.
With this release, upstream has stopped distributing documentation in
release tarballs, instead we have to generate it. Hence, most of the new
dependencies are for this purpose.
The configure_args part is for detecting this in cross.
The hack for cross has been removed as this is actually a reccuring
issue with ppc cross that will be seperatly addressed, generally, for
all packages.
Tests are currently not working, @ericonr you looked at this before would you mind looking at it again and seeing if you can get it to work? I had a preliminary look, but couldn't make much sense of the weird QT path things... I don't really care about tests for this because they are "unsupported" by upstream.
prev parent reply other threads:[~2020-12-12 6:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-26780@inbox.vuxu.org>
2020-12-06 4:31 ` fosslinux
2020-12-12 6:50 ` ericonr
2020-12-12 6:50 ` ericonr [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=20201212065046.mJUPUAxHAF56lH1LzWSZuXZRxd5gEOaazmsexgC7_Wo@z \
--to=ericonr@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).