devel/ffcall: updated to 1.13, take maintainership

[ultima]

Summary

• Updated to 1.13
• New maintainer Jov <[e-mail]>
• License changed to GPLv2+

Changelog: https://lists.freebsd.org/pipermail/freebsd-ports/2017-June/109211.html

PR\: 220250
Sumitted by\: Jov <[e-mail]> (maintainer)
Reviewed by\: lifanov (mentor), matthew (mentor)
Approved by\: lifanov (mentor), matthew (mentor)
Differential Revision\: https://reviews.freebsd.org/DXXXXX

Test Plan

portlint:
WARN: Makefile: for new port, make $FreeBSD$ tag in comment section empty, to make SVN happy.
0 fatal errors and 1 warning found.

poudriere:
103i386
103amd64
110i386
110amd64
12i386
12amd64

[ultima]

The maintainer is planning on changing the name to libffcall after the update.

[ultima]

• Changed hardcoded portname to ${PORTNAME}

[lifanov]

Is there a reason for removing BROKEN_* stuff?
Did something change that would make the port work
on these platforms or did the submitter test it, etc.?

[ultima]

In D11428#236418, @lifanov wrote:

Is there a reason for removing BROKEN_* stuff?
Did something change that would make the port work
on these platforms or did the submitter test it, etc.?

Yes, it was fixed upstream. https://lists.freebsd.org/pipermail/freebsd-ports/2017-June/109211.html

[ultima]

Also, I couldn't find a good changelog to use in the url, I am going to add that post as the changelog as it is informative about the updates.

[matthew]

This looks good to me as it is, but why not do the proposed rename at the same time?

[ultima]

In D11428#236532, @matthew wrote:

This looks good to me as it is, but why not do the proposed rename at the same time?

I think it is better to keep the rename and depends change commit together but separated with an update commit because it is two different types of commits. Would it have been okay to roll it into into one commit?

[mat]

head/devel/ffcall/Makefile

26–28

This could probably be:

@${STRIP_CMD} ${STAGEDIR}${PREFIX}/lib/*.so