new package: mdbook-epub
This commit is contained in:
parent
c72ad9fbb1
commit
ea8e9afb68
|
@ -0,0 +1,31 @@
|
|||
TERMUX_PKG_HOMEPAGE=https://github.com/Michael-F-Bryan/mdbook-epub
|
||||
TERMUX_PKG_DESCRIPTION="An EPUB renderer for mdbook"
|
||||
TERMUX_PKG_LICENSE="MPL-2.0"
|
||||
TERMUX_PKG_MAINTAINER="@termux"
|
||||
TERMUX_PKG_VERSION=0.4.14
|
||||
TERMUX_PKG_SRCURL=https://github.com/Michael-F-Bryan/mdbook-epub/archive/refs/tags/${TERMUX_PKG_VERSION}.tar.gz
|
||||
TERMUX_PKG_SHA256=d2cf2c38c50a3eb476c14854f395ce3423ec58ddc310699d747df5a6f37f6cf1
|
||||
TERMUX_PKG_BUILD_IN_SRC=true
|
||||
|
||||
termux_step_pre_configure() {
|
||||
termux_setup_rust
|
||||
|
||||
: "${CARGO_HOME:=$HOME/.cargo}"
|
||||
export CARGO_HOME
|
||||
|
||||
cargo fetch --target "${CARGO_TARGET_NAME}"
|
||||
|
||||
local _patch=$TERMUX_PKG_BUILDER_DIR/mdbook-src-renderer-html_handlebars-helpers-navigation.rs.diff
|
||||
local d
|
||||
for d in $CARGO_HOME/registry/src/github.com-*/mdbook-*; do
|
||||
patch --silent -p1 -d ${d} < ${_patch} || :
|
||||
done
|
||||
}
|
||||
|
||||
termux_step_make() {
|
||||
cargo build --jobs $TERMUX_MAKE_PROCESSES --target $CARGO_TARGET_NAME --release
|
||||
}
|
||||
|
||||
termux_step_make_install() {
|
||||
install -Dm700 -t $TERMUX_PREFIX/bin target/${CARGO_TARGET_NAME}/release/mdbook-epub
|
||||
}
|
|
@ -0,0 +1,37 @@
|
|||
https://github.com/rust-lang/mdBook/commit/8f01d0234f708042ea8d0dc5cac63859b3f14cb1
|
||||
|
||||
From 13035baeae417e41ce98f49c072220de0e6e4075 Mon Sep 17 00:00:00 2001
|
||||
From: mitchmindtree <mail@mitchellnordine.com>
|
||||
Date: Fri, 22 Jul 2022 15:10:05 +1000
|
||||
Subject: [PATCH] Workaround rust nightly borrowcheck error (#1860)
|
||||
|
||||
Surprisingly, this fixes the error filed at #1860!
|
||||
|
||||
This seems suspicious, perhaps indicative of a bug in Rust's non-lexical
|
||||
lifetime handling?
|
||||
|
||||
The lifetimes in the `handlebars::Renderable::render` method signature
|
||||
are quite complicated, and its unclear to me whether or not Rust is
|
||||
catching some new safety edge-case that wasn't previously handled
|
||||
correctly...
|
||||
|
||||
Possibly related to `drop` order, which I *think* is related to the
|
||||
order of binding statements?
|
||||
---
|
||||
src/renderer/html_handlebars/helpers/navigation.rs | 2 +-
|
||||
1 file changed, 1 insertion(+), 1 deletion(-)
|
||||
|
||||
diff --git a/src/renderer/html_handlebars/helpers/navigation.rs b/src/renderer/html_handlebars/helpers/navigation.rs
|
||||
index d3f6ca9086..65929bbfc1 100644
|
||||
--- a/src/renderer/html_handlebars/helpers/navigation.rs
|
||||
+++ b/src/renderer/html_handlebars/helpers/navigation.rs
|
||||
@@ -149,8 +149,8 @@ fn render(
|
||||
_h.template()
|
||||
.ok_or_else(|| RenderError::new("Error with the handlebars template"))
|
||||
.and_then(|t| {
|
||||
- let mut local_rc = rc.clone();
|
||||
let local_ctx = Context::wraps(&context)?;
|
||||
+ let mut local_rc = rc.clone();
|
||||
t.render(r, &local_ctx, &mut local_rc, out)
|
||||
})?;
|
||||
|
Loading…
Reference in New Issue