Revert the last changes, plus removing NO_BUILD.

Add patch brought by @mikael.urankar_gmail.com :

Removing gnome-shell stuff.

Quick update of devel/ocaml-camlp4 to 4.07+1.

Fix "themes" directory creation.

• fix ocaml-nox11 conflict - add CONFLICT_INSTALL
• remove MAKE_JOBS_UNSAFE - this apparently is safe to do.

Improve documentation leftovers remotion.

Bring STRIP back. This is actually needed. ^^

Building with GCC8 doesn't change the warnings and errors.

Remove STRIP, OPTIONS_SUB - they aren't doing anything. Add OPTIONS subs to pkg-plist.

In D19318#413631, @tobik wrote:

Thanks for trying to update lang/ocaml. Have you seen https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218333 ?

In D19301#413325, @uzsolt_uzsolt.hu wrote:

In D19301#413319, @tcberner wrote:

Looks good to me.
If the two maintainers are happy with it too, go for it.

If zathura works with mupdf plugin (now I can't test it) for me it's okay.

In D19301#413322, @tcberner wrote:

ah wait, was removing the NLS optiona intentional? :D

Remove gmake from graphics/zathura-pdf-mupdf. Not needed.

In D19301#413297, @uzsolt_uzsolt.hu wrote:

Can you view pdf files with zathura?

• remove jpeg-turbo from BUILD_DEPENDS in graphics/mupdf
• remove + from MESON_ARGS in zathura-pdf-mupdf

Cleaning.

Remove LICENSE_FILE.

LICENSE_FILES ---> LICENSE_FILE

There is a problem with luatex:

From the Handbook:

I've updated to 2.9.6975, added some OPTIONS, and shut portlint. There are more OPTIONS opportunities like INSTALL_MIKTEX_HEADERS (fail to build with some Linux file missing) and WITH_LUA54TEX (lua54 is not in ports yet).

• add kde:5 to USES
• add patch to fix the Qt5 version build

Removing DAEMON from OPTIONS_DEFAULT in the meta port.

Add the previously forgotten -web.

However my doubt was more related with the concept differences of flavors and sub-packages (slaveports in practice), like happened with transmission-* when flavoring everything (cli, daemon, gtk, qt, web) in a single port instead of separated slaveports for cli, daemon, gtk versions, qt versions, and web in D16387.

In D18840#404669, @mat wrote:

The only thing that comes to mind that might not work and require a slave port is the dependency of some flavors to another, but I don't think it is the case, I don't remember if I ever tested that.

In D18840#404565, @mat wrote:

Mmmm, why create a slave port instead of adding a first, say, core, flavor to libfm?

Everything building now, and Qt related ports bumped. \o/

Do svn cp of libfm.

Updating patch as per submitter.

Parsing -B instead of using Makefile variables. :-D

Cleaning unneeded lines.

Thanks to tcberner. :-D

In D18770#400757, @tcberner wrote:

In D18770#400694, @rigoletto wrote:

Add support for all supported python versions.

The thing is, doing it like this you now need to remember to update the patch whenever a new verison appears. This seems too tedious :) -- How about just s/python2 python2.7 python3 python/pyhton${PYTHON_VERSION}/ in the file on that line?

Add support for all supported python versions.

In D16387#400407, @tcberner wrote:

Looks good to me. Do you have the maintainers approval?

In D18517#398491, @tcberner wrote:

I think you can commit this now.

Reverting the Created by line.

In D16387#398067, @mat wrote:

Why do you remove all the Created by lines, were those removal requested?

In D18660#398068, @mat wrote:

If it is only the build being fixed, why bump PORTREVISION?