@mat Can this be committed?

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

Ok!

In D11977#250961, @mat wrote:

dep_file is supposed to be immutable. Do not modify it .

Updated to match 3 NVidia GL libraries.

Added comment.

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

Updated according to Mat's suggestions.

Updated according to Mat's suggestions.

In D11095#242930, @koobs wrote:

-1 on pkg being the place to solve this. Though there may be merit in improved conflicts handling (in certain limited cases) in pkg in general, I'd like not to have the path of least resistance for porters/maintainers be let a tool handle an issue rather than do it properly (where properly means ports should not conflict in the first place)

Here is an idea for a different approach.

What is holding this?

Yes, but outside of a testing/QA environment, they are the same, and symlinks should be relative within.

I couldn't update this diff. It only offers to create a new revision. So I write in words:

I integrated your patch into https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218985
Please commit it if you can.

Please note that there is a pending update: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218985

Agreed.

Thanks a ton for the port, and for helping me to being able to use it!

[: =: unexpected operator

All of them are listed here: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205053:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204904
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204577
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204772
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204932
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205032

It looks like you possibly missed this patch https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205032
This patch (bug#205032) also breaks on 9.X, so you need to use 10.X for now.

I think phabricator workflow is broken, doesn't allow me to add a new patch. It first says "Update patch for D4514", but when I upload the patch it only offers me to create or update the new diff number.

@jbeich The problem with parsing json with awk is that this is generally not a proper way to parse json. The right way is to use textproc/jq utility, but ports framework doesn't have access to jq. When you parse with awk, you don't rely only on GitHub API, you also rely on the particular way how they format their json output, which might change any time. Please keep in mind that they may also expand their json output any time, and this won't be considered the violation of API as long as all parts of the older structure are still present. And awk expressions will just fail.

@jbeich These targets were originally meant for information only, to avoid going into each individual project and compare last revisions.

Matt, the modified targets don't work.