Re: port of INSTALL file generation to XSLT

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
Cc: Mi Tar <mmitar(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: port of INSTALL file generation to XSLT
Date: 2019-01-11 21:05:05
Message-ID: 30500.1547240705@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I wrote:
> 1. No pandoc on borka, where we build tarballs:
> pgsql(at)borka:~$ which pandoc
> pgsql(at)borka:~$

That part's sorted, anyway.

pgsql(at)borka:~$ pandoc --version
pandoc 1.17.2
Compiled with texmath 0.8.6.7, highlighting-kate 0.6.3.
Syntax highlighting is supported for the following languages:
...

> 2. If there's no pandoc, this coding silently produces a zero-size
> INSTALL file. I do not find that acceptable.

Seems like it might be sufficient for the rule to be

$(PANDOC) $< -t plain > $(at)(dot)tmp
$(ICONV) -f utf8 -t us-ascii//TRANSLIT < $(at)(dot)tmp > $@
rm -f $(at)(dot)tmp

Failure would leave a .tmp file behind, but I doubt we care enough
about that to work harder than this.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2019-01-11 21:11:01 Re: Policy on cross-posting to multiple lists
Previous Message Magnus Hagander 2019-01-11 20:25:56 Re: Checksum errors in pg_stat_database