[Bug 259669] comms/xastir update from 2.1.6 to 2.1.8

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259669

            Bug ID: 259669
           Summary: comms/xastir update from 2.1.6 to 2.1.8
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: ports-bugs@FreeBSD.org
          Reporter: russo@bogodyn.org
                CC: carl@stagecraft.cx
             Flags: maintainer-feedback?(carl@stagecraft.cx)
                CC: carl@stagecraft.cx

Created attachment 229305
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=229305&action=edit
Patch to update comms/xastir to version 2.1.8

The Xastir group released version 2.1.8 a couple of weeks ago.  It is mostly a
maintenance release, and is easy to update.

The main "gotcha" is that the Github releases no longer come "pre-bootstrapped"
--- they contain no "configure" script or any other autotools-produced files,
nor are some of the other files produced by the "bootstrap.sh" present.

The attached patch should completely prepare the port for the new version.  I
have tested it out and it works seamlessly with all the existing patch files as
before.

Unfortunately, this is the first time I have ever tried to build the Xastir
port in FreeBSD (I am an Xastir developer, and always build it from source
myself), and I find that Xastir's probe for "gv" actually tries to *run* gv in
order to get its version number, and this does not work when building through
the port for reasons I don't understand (it gets a strange error when trying to
run "gv --version", and interprets this as gv not being usable, so it skips
using it).  But that was already the case before my changes, and means one
can't print map screens  --- but apparently one never could with the port-built
Xastir.

At any rate, my patch updates the port to 2.1.8 and the build is just as
functional as it was with 2.1.6.

The patch was created from a private git branch using "git format-patch".

-- 
You are receiving this mail because:
You are the assignee for the bug.