+= is a good idea.

I'd rather you omit other changes like this.

No.

no_env does not seem to be documented.

Hmm, it doesn't seem to do anything in USES=qt. Looks like the usage comment at the top of qt.mk is not correct.

no_env gets interpreted by qmake.mk

^ no_configure and no_env are mostly for internal use [and very broken software].

^ I'm not sure at the moment if that made it into the committed version :) -- it works for qt-dist.mk, but I have to double check for qmake.mk

I wonder if these paragraphs should be removed or moved to the qmake section instead (with QT_NONSTANDARD -> USES= qmake:no_env)? qt.mk does not seem to modify CONFIGURE_{ENV,ARGS} much on its own.

Should I

a) remove the description of no_env and no_configure again?
b) add a "For interal use only." note?
c) add a warning that they probably shouldn't be used by porters?

Trying to build a port with just USES=qmake:5 or USES=qmake:4 fails with:

Incorrect 'USES+= qmake' usage: argument '4' is not recognized.

I'll remove the tip again.

I think I prefer c) something like "In most cases these are not needed"

Ah, yes, QT_NONSTANDARD was removed some time ago, I missed that.

I would phrase this a bit differently, something along the lines of if the software breaks this or that way, use no_env/no_configure. The goal of the handbook is to help porters port software, it is better to say "use in this case" rather than "you will probably not need it".

You should add no_env back, it is a valid argument, maybe saying that it is passed to qmake.

• no-configure: required if the software requires qmake, and the environnent variables set by qmake.mk at build time, but the build system is not qmake based
• no-env: required when qmake is used to configure the software, but fails to understand the environment setup by qmake.mk.

Extra \n inside <literal>.

There's an extra "\n" inside the <command> tag.

Remove extra blank line.