liburcu is identical to already existing userspace-rcu

[barracuda156]

As far as I can tell, new liburcu port is identical to existing userspace-rcu, though lacking some needed fixes like C++11 standard. What was the reason to introduce it?

[danielluke (Daniel J. Luke)]

Because I didn’t find it when I looked for it in macports.

[barracuda156]

Replying to danielluke:

Because I didn’t find it when I looked for it in macports.

What do we do now? )

16. S. If this port is gonna stay, we need to borrow patches and cxx_standard from userspace-rcu.

[danielluke (Daniel J. Luke)]

We should switch to the existing port (and maybe also make a patch for it to make it more discoverable).

I’ll try to test out how we do this in a minimally disruptive way (probably need to mark the new port as replaced by the old one).

[danielluke (Daniel J. Luke)]

• added 'liburcu' to the userspace-rcu description (port search liburcu and port search urcu both find it now).
• tested changing bind9 dependency and marking liburcu as obsolete, on my machine it installed userspace-rcu, deactivated librcu, and rebuilt bind9