Github messages for voidlinux
 help / color / mirror / Atom feed
From: mtboehlke <mtboehlke@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] New package: tth-4.15
Date: Sun, 29 Aug 2021 02:08:53 +0200	[thread overview]
Message-ID: <20210829000853.IvyjFpTEpXMMhyrSImO33FsBPxjNLKZ7SQvPBsVictY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32740@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1869 bytes --]

There is an updated pull request by mtboehlke against master on the void-packages repository

https://github.com/mtboehlke/void-packages tth
https://github.com/void-linux/void-packages/pull/32740

New package: tth-4.15
<!-- Mark items with [x] where applicable -->

#### General
- [x] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)

#### Have the results of the proposed changes been tested?
- [x] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me

<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->
<!-- 
#### Does it build and run successfully? 
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [ ] I built this PR locally for my native architecture, (ARCH-LIBC)
- [ ] I built this PR locally for these architectures (if supported. mark crossbuilds):
  - [ ] aarch64-musl
  - [ ] armv7l
  - [ ] armv6l-musl
-->

TtH is a standalone TeX to HTML translator that directly translates equations, rather than converting them to images.  It requires external programs only when trying to handle embedded graphics (e.g. postscript figures), or if you are using the picture environment, in which case you will need to have `latex` and `dvips` available, presumably from texlive.

A patch file from https://github.com/void-linux/void-packages/pull/32740.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-tth-32740.patch --]
[-- Type: text/x-diff, Size: 1108 bytes --]

From 5dbd1940710c188b42364ce85e3f5e724d8b18ef Mon Sep 17 00:00:00 2001
From: Mat Boehlke <mtboehlke@gmail.com>
Date: Fri, 27 Aug 2021 14:17:53 -0500
Subject: [PATCH] New package: tth-4.15

---
 srcpkgs/tth/template | 23 +++++++++++++++++++++++
 1 file changed, 23 insertions(+)
 create mode 100644 srcpkgs/tth/template

diff --git a/srcpkgs/tth/template b/srcpkgs/tth/template
new file mode 100644
index 000000000000..6aec4ccd5cd8
--- /dev/null
+++ b/srcpkgs/tth/template
@@ -0,0 +1,23 @@
+# Template file for 'tth'
+pkgname=tth
+version=4.15
+revision=1
+wrksrc="tth_C"
+depends="ghostscript netpbm"
+short_desc="TeX to HTML translator"
+maintainer="Matt Boehlke <mtboehlke@gmail.com>"
+license="custom:TtH"
+homepage="http://hutchinson.belmont.ma.us/tth"
+distfiles="${homepage}/tth-noncom/tth_C.tgz"
+checksum=83c1f39fbf3377fb43e3d01d042302fa91f8758aa9acc10e22fe8af140f0126c
+
+do_build() {
+	${CC} -o tth ${CPPFLAGS} ${CFLAGS} tth.c ${LDFLAGS}
+}
+
+do_install() {
+	vlicense license.txt LICENSE
+	vdoc tth_manual.html
+	vman tth.1
+	install -t "${DESTDIR}/usr/bin" -Dm755 tth ps2png ps2gif latex2gif
+}

  reply	other threads:[~2021-08-29  0:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-28 22:54 [PR PATCH] " mtboehlke
2021-08-29  0:08 ` mtboehlke [this message]
2021-10-04  0:49 ` mtboehlke
2021-10-04  0:49 ` [PR PATCH] [Closed]: " mtboehlke
2021-10-04  0:49 ` mtboehlke
2021-10-04  0:50 ` mtboehlke
2021-10-04  0:50 ` mtboehlke

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=20210829000853.IvyjFpTEpXMMhyrSImO33FsBPxjNLKZ7SQvPBsVictY@z \
    --to=mtboehlke@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).