did you check if the dependencies break?

• devel/rubygem-gitlab_git
• net-im/mastodon
• textproc/rubygem-github-linguist
• textproc/rubygem-gitlab-grit
• textproc/rubygem-gitlab-linguist
• www/gitlab

I'm still confused about all your pear-Updates. At first: it removes the usage of pear. Okay, PEAR was gone and resurrected and many projects went away. Fine.
But:

1. pear is still in the package name even if its not used
2. When read correct (i'm unsure): you add the pear-channel as RUN/BUILD dependency for the script itself without using any pear-functionality at all?
3. Downloading it plainly from GitHub and executing it and the test-cases is just fine So: why even bother with the depends?

Since PR and Review are nearly identical and you are not the author: did you check everything the patch should do? And i do not mean just a build-test. I mean "try to reproduce the error, test the patch, is it gone and everything else works still fine"?
Also the long list of portlint output is quite frightening :D

I change the status of the review to make clear, that changes are needed

pkg-static: Warning: @exec is deprecated, please use @[pre|post][un]exec

pkg-static: DEVELOPER_MODE: Notice: arch "FreeBSD:11:i386" -- no architecture specific files found:

• could this package use a wildcard architecture?

exp-run requested in: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221792

Change check for bundle according to mat's suggestion

In D11954#248065, @joneum wrote:

In D11954#248051, @tz wrote:

Approved with following changes:

• Changelog URL should be: https://wiki.typo3.org/TYPO3_CMS_8.7.4
• Add MFH for 2017Q3

Can you give me a hint - why MFH? I only see into the Changelog, that this update have bug fixes only.

Approved with following changes:

Approved with following changes:

• Changelog URL should be: https://wiki.typo3.org/TYPO3_CMS_7.6.21
• Add MFH for 2017Q3

Poudriere works with PHP 56 and cannot installed this Port (doesn't support PHP 5.6)

Overcome by events

Was committed yesterday and can be closed :)

• Switch from error to warning in Output
• remove return value of 1 when finding error

• use guards instead of too many ifs
• add USE_RUBY check
• add check for existing bundle before using
• change var-name from GemfilePath to f
• quote variable in if-conditions

I fixed the usage of the variables, which seems to work just out of curiosity.
I also added an error message for WIP reasons. Currently the check does not work in any circumstance and i currently do not understand why. This needs some more investigation.

I'm sorry, i mixed up my comments and the diff-update. I really need to get more used to it.

In D11823#245207, @mat wrote:

In D11823#245167, @tz wrote:

That did the trick, thanks! :) But what does this option do?

So, you are a ports committer, and you have not read the porter's handbook ? 5.13. Makefile Options