[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
bugzilla-noreply at freebsd.org
Wed May 8 20:10:16 UTC 2019
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234669
--- Comment #15 from Tobias Kortkamp <tobik at freebsd.org> ---
(In reply to Lorenzo Salvadore from comment #14)
> 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.
I would not waste your time on vdr-plugin-upnp. All multimedia/vdr* ports
should probably be removed as they haven't really been updated in 6 years
and are based on an old developer snapshot of vdr. I doubt updates of it
are trivial either given the amount of patches in some of them. I wonder
if there are even users of it left too.
I deprecated djmount and vdr-plugin-upnp with expiration date of next week.
Let's see if somebody complains and if not go ahead with the update to 1.8.
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-ports-bugs
mailing list