New port: audio/eq10q-lv2: Parametric equalizer LV2 audio plugin

[yuri]

Summary

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

[tcberner]

You need to add a SUBDIR += eq10q-lv2 line to audio/Makefile

audio/eq10q-lv2/Makefile

2

^ These comments are being phased out [afaik], so I would not add them anylonger.

6

^ DISTVERSION is prefered over PORTVERSION

22

^ I would use cmake:outsource if it's possible

36

^ using patches in files/ is often more readable than sed-calls.

[mat]

audio/eq10q-lv2/Makefile

33

If this is for 10, it should be done with an OSVERSION check, so that it can be removed when the version of FreeBSD is not supported any more.

[dbaio]

audio/eq10q-lv2/Makefile

11

@FreeBSD.org

[yuri]

audio/eq10q-lv2/Makefile

22

Only <30% of cmake ports use cmake:outsource. Normally, cmake projects build fine in-place. cmake:outsource is for situations when in-place build breaks. It usually breaks due to bugs.

I think, USES=cmake is a good default.

33

This option fails in 10, but it is also not needed in general. This option is only meaningful in conjunction with the 'inline' keyword, that is deemed obsolete by clang (gcc might still make use of it).

I will clarify the comment.

36

Recently another committer, ultima@, convinced me that the opposite is true for one-liner comments.

Also, section 4.4.3 says "Simple replacements can be performed directly from the port Makefile using the in-place mode of sed". All these are one-line changes in each instance.

[tcberner]

audio/eq10q-lv2/Makefile

36

It's down to taste, but in a patch-foo you always at least have some context around the change, which you don't have in the sed-calls.

[mat]

audio/eq10q-lv2/Makefile

22

Well, not really, only <30% of ports use cmake:oursource because someone has not gone and replaced the rest with cmake:outsource, it should probably be the default, please, change it to cmake:outsource.

36

I agree with @tcberner here, use patches when possible (so, when you are not replacing by something variable), otherwise, you end up having a dozen sed one-liners that you have no idea if they are still:

1. useful
2. needed
3. doing something

With a patch, you know right away if it is still needed or not.

[yuri]

Requested changes.

[yuri]

@tcberner

Tobias, it seems that everything has been resolved, and it achieved the state of uncontroversialness. :)

[tcberner]

Looks good.

audio/eq10q-lv2/Makefile

22

^ as a warning for the future. dos2unix eats everything - even binaries

[yuri]

audio/eq10q-lv2/Makefile

22

Ok.