[Xastir] FreeBSD port for Xastir 2.1.4 submitted.

[Tom Russo]

On Tue, Jul 16, 2019 at 11:29:20AM +1000, we recorded a bogon-computron collision of the <carl at stagecraft.cx> flavor, containing:
> Hi Tom,
> 
> > On 15 Jul 2019, at 11:27 pm, Tom Russo <russo at bogodyn.org> wrote:
> > Is there a reason you had to remove all reference to imagemagick?  Xastir
> > still builds with either ImageMagick or GraphicsMagick, and we test both.  
> > There was brief discussion of removing ImageMagick support, but we discarded
> > that idea.  
> 
> Oh.  I was under the impression that Xastir had standardised on GraphicsMagick.  I must have missed where that idea was discarded.  My apologies.

Years ago, ImageMagick was so frequently breaking their API that we went to
preferring GraphicsMagick -- if configure detects both, it uses GraphicsMagick.
But if only IM is installed, or if both are installed and GM doesn't work,
we use IM.

For some years, that frequent API breakage caused havoc in Xastir, and the 
code is peppered with all sorts of ifdefs to work with any version of 
IM it finds.  That led to a bit of annoyance and frequent suggestions of
dropping IM support and requiring GM.  But we couldn't do it at one point, 
because some systems in those days wouldn't let you have both GM and IM 
installed at the same time (at least some version of Ubuntu had them so they 
conflicted with each other), and some programs our users wanted *required* IM.

Those "frequent" API changes appear to have stopped many years ago, and the 
code is stable now.  So the need to chase changes went away, as did any real 
impetus to drop IM support.  We will continue to work with both for as long as 
possible.  The only thing under discussion these days is removing all those
old hacks that let ancient versions of IM continue to work (they're now so
old nobody has them installed, so why keep the code bloat?).

Right after I upgraded to FreeBSD 11, I discovered that my Xastir build
(which explicitly used Clang on BSD 10) stopped picking up GM even though it
was installed --- that's because the configure probe for GM was failing due
to the OMP stuff when building with clang.  So I do know that the configure 
stuff properly falls back to IM if it can't find a *working* GM.

> I???ll stop the current port update and add ImageMagick back into the port as the default. That will stop it wanting gcc8 as well.  

If a user asks for GM, you'll need to use gcc8, but if you use IM as the 
-- 
Tom Russo    KM5VY
Tijeras, NM  

 echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] [n-z][a-m]