Looks good to me. Let's just get the outdated file into shape, do an exp-run and commit it.

Quoting "marino (John Marino)" <phabric-noreply@freebsd.org>:

Quoting "marino (John Marino)" <phabric-noreply@freebsd.org>:

Quoting "marino (John Marino)" <phabric-noreply@freebsd.org>:

The commit message (after @antoine's mentioned exp-run) should also include a link to the upstream changelog and highlight the most important changes for this release

Excellent, thanks. @madpilot: accepted.

Looks good to me.

In D1831#8, @AMDmi3 wrote:

Even though any valid non-empty USE_SDL= adds libSDL.so or libSDL2.so to LIB_DEPENDS ?

Yes. Actually, this may not even be correct, or may be changed in future.
What matters though is not what ports framework implicitly assumes, but what port actually uses. As long as it calls sdl_config or links with -lSDL, which belong to SDL, it should explicitly depend on SDL. Same with gnome stuff.

No. All (official) SDL_XXX libs also have a -lSDL linker target in their .pc and .la files. And all of them require a call to the SDL_Init() function.

That is not correct. At least SDL2_ttf does need SDL_Init and its documentation explicitly says so.

In D1831#5, @jbeich wrote:

In D1831#4, @AMDmi3 wrote:

Drop implicit USE_SDL=sdl (see _REQUIRES_xxx in bsd.sdl.mk)

Please don't. As long as the game explicitly links with -lSDL, there should be explicit USE_SDL=sdl.

Even though any valid non-empty USE_SDL= adds libSDL.so or libSDL2.so to LIB_DEPENDS ? This is similar how many ports with USE_GNOME=gtk20 actually mean USE_GNOME=glib20 gtk20. Explicit dependencies are only useful if there's a way to avoid them and I don't mean indirect linking.

@mva: Can SDL libs be used standalone? For example, SDL_image without SDL itself.

Committed, thanks!

In D1416#5, @antoine wrote:

More ports not converted:

...

databases/postgresql84-plpython/Makefile:WANT_PYTHON_USE= python:2
databases/postgresql90-plpython/Makefile:WANT_PYTHON_USE?= python

Closed by commit rP375220 (authored by @mva).

Does not it need django as well?

Committed.

In D573#30, @wblock wrote:

Let's just commit this. Please build-test first, though.

Committed in rP371447.

• Readded double space
• Added "see also" link

Oh my, I completely forgot about the non-Python world, when doing this. Let me think about those cases once more and how to identify the ports. A quick solution that comes to my mind would be something along the lines

• Try to get another comma right

• Improve "concurrent" description
• Fix comma (hopefully)

I do not have the time to create a more elaborate documentation at the moment and we should not keep the handbook outdated until I'm done with anything related to that.
Instead, I would want to see the current changes and updates to be pushed into the docs.

• Fix typos
• Add small example

Committed in rP369800.

Committed in rP369796.

Yes, I just got distracted, sorry.