[Bug 234669] devel/upnp: Adds new options; updates to 1.8.4 or prepares port for being used as masterport

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234669

--- Comment #14 from Lorenzo Salvadore <phascolarctos at protonmail.ch> ---
I tried to work on bug #237404 and #237409 to fix them, but I think the two
softwares are too old to use upnp branch 1.8.x:

- djmount is more than 10 years old and everytime I fix a problem a new problem
comes up (and the last one looks to be too big to be solvable without rewriting
much of the source code);
- I am still working on vdr-plugin-upnp; the actual version looks to be quiet
difficult to build with upnp 1.8.x, but I have discovered that the port is out
of dat, then I will try to update it (but still the last release is from 2013).
Moreover, the port is unmaintained: maybe nobody is really interested in it.

As I said, I will keep trying with vdr-plugin-upnp, but I think we have to
possibilities:

1) maintain two ports -- upnp and upnp18 (or upnp16 and upnp)-- as I initially
suggested, so that we do not lose any port;

2) update the original upnp port to the 1.8.x branch, but this will require
removing from the ports tree those ports that can not be built with the new
branch (djmount and, probably, vdr-multimedia-plugin).

-- 
You are receiving this mail because:
You are the assignee for the bug.