[GF-Users] postfix-tlspol: Upstream updated to 1.11.0
Peter
peter at pajamian.dhs.org
Tue Jul 14 02:23:46 MST 2026
On 14/07/2026 17:32, Michael Webb wrote:
>> The new patch adds a clarification to help users how to read upstream
>> md file format.
>
> I'm thinking it might be better to compile the markdown to a standard text file, then no special reader will be necessary. I'll do that and update the patch accordingly.
>
> **********************************************************************************************************************************************************
> I did spend a few hours on this to convert md, but it started to look and feel terrible - when really, all a user has to do is visit the upstream website to get the same information in a more presentable format and when glow already works very well in putty.
>
> I tried running pandoc with only limited success, and finished using the regexp with philosophy below which worked very well:
>
> First copy SourcePath/README.md to BuildPath/README.md.orig, then
> cat SourcePath/README.md | \
> sed -E '/\!\[/d; /<img/d; /<br/d; /<details>/d; /<\/details>/d; /<summary>/d; /<\/summary>/d' | \
> sed -E 's/\[([^]]+)\]\(([^)]+)\)/\1 (\2)/g; s/<[^>]*>//g; s/\\_/_/g; s/`//g; s/^#+[[:space:]]*//g' \
> > "BuildPath/README.md"
> ********************************************************************************************************************************************************
Glow isn't in any of the standard repos that I can find for EL. At the
end of the day my goal is to allow people to read the included docs
without the need for software that has to come from side-channels, so
converting to text seems to be the answer. It doesn't have to look
pretty, it just has to be readable and contain the necessary info.
I went with pandoc because that is packaged for the various EL releases
(in PowerTools/CRB for EL8 and EPEL for 9 and 10) so it's easy to make
it a BuildRequires and call it from the %install script. It does
generate a serviceable plain text file, imo, and as you point out
someone who wants to see it with all the bells and whistles can always
view it on the website. The command I used was simply:
pandoc -f markdown -t plain < README.md > README
Peter
More information about the users
mailing list