Thanks for taking the effort to bring naming consistency across both src and ports. Can someone tell the story what was wrong with NETWORK (shorter base form) that it had to be replaced with NETWORKING (longer gerund form)? Or it simply better describes the matter, English-wise?

Looks good; I also like how some previously overly long comments had been reworded for clarity and brevity.

@ivy wrote:

no, but it is no longer supported, so we don't need to support it. it would be different if it had been downgraded to tier 3 rather than becoming entirely unsupported.

Admittedly, I don't see much difference between being demoted to T3 vs. unsupported, although it's another topic. I think we could retain 32-bit PPC support due to mass production of good quality Apple G4 hardware which is scattered around the world and is still useful as a backup boxen, NAS, etc. Another reason to keep it around: different endianness, char signness, 32-bitness force one to write well-typed, correct, sound code. And it's not affected by Y2038 problem, i.e. uses 64-bit time_t.

@salvadore wrote:

IMHO, make -V WWW is the way to go.

@adamw wrote:

A request: for clarity, can reboot(8) explicitly say something to the effect of "reboot is equivalent to shutdown -r now"?

@mat wrote:

The ports tree is to be used by developers, not end users. End users have packages and should not have to interact with the ports tree ever.

@asomers wrote:

The only thing I wanted different is a more detailed commit message. Of course, Mark might disagree.