Eventually, PR 199134 can be considered related.

I see. I remembered having seen man-compress magic in post-build at some ports and wondered where it went...

Uploaded a new diff with a small explanation in it's header.

It went into PORTS in revision 385795.

Last patch lacked pkg-plist

Merge r10677 from area51: Install the man page into the right path

Patch commited in PORTS revision 381052.

The patch in diff 3 (4001) seems to lack Makefile changes to the alsa patching for some reason, and r10601 was missing in that patch.

Added all area51 commits recently done which address the commented issues. Also added svn properties which were missing in the last patch.

Updated the patchset to also contain the area51 commits mentioned in the opening post, as well as

Closed by commit rP374791 (authored by @alonso).

Closed by commit rP374787 (authored by @alonso).

Update the patch to contain the recent area51 commits affecting telepath.

Added more comments.

Closed by commit rP373980 (authored by @alonso).

Regenerate the patch to partially revert area51's revision 10488. While area51 doesn't use PORTREVISION, the area51 version being more recent is wrong as kdevelop-pg-qt doesn't share kdevelop's version, so reintroduce PORTREVISION.

Regenerate patch to not undo ports revision 373662 and contain area51 revision 10488

Commited to ports in revision 372093. We might want to prever Avahi over mDNSResponder in cups too which I'm proposing D1084.

Updated patch - Overload mDNSResponder description to display issues with KDE.

In D1031#13, @rakuco wrote:

Now it makes sense to bump PORTREVISION ;-) Since this version of the patch removes dependencies from the port, you need to bump PORTREVISION.

In D1031#10, @makc wrote:

In D1031#9, @rakuco wrote:

Avahi is used by some other ports, but in 2007 there were less Avahi users and therefore less chance to have Avahi installed and silently be used by kdelibs, so back then it might have been in use by more people.

Not really, unless I'm missing something obvious: since in addition to the dependency on net/avahi-libdns via the "AVAHI" option we've always depend on net/avahi-app, which contains the header that is used to detect Avahi's presence by kdelibs.

Note that removing MDNSRESPONSER wouldn't introduce a hard dependency on AVAHI, as kdelibs provides a dummy backend if no ZEROCONF backend is found.

The dummy backend is only built if neither mDNSResponder nor Avahi are found, but since we always depend on the port that provides the header used to check if Avahi is present or not, we'd still have a hard dependency on Avahi. This would only change if the dependency on net/avahi-app became optional.

I go for simplicity: lets leave hard dependency on avahi-app and remove ZEROCONF/AVAHI/MDNSRESPONDER options.

I've updated the patch. I was using capitalized constants because that's how they're listed in http://www.cmake.org/Wiki/CMake:VariablesListsStrings and thought bumping PORTREVISION was ok as previous builds might have an untracked runtime dependency on Avahi.