Page MenuHomeFreeBSD

net-im/tox: upgrade to v0.2.0

Authored by thierry on Mar 1 2018, 9:01 PM.
Referenced Files
Unknown Object (File)
Sun, Nov 12, 1:32 AM
Unknown Object (File)
Fri, Nov 10, 11:43 AM
Unknown Object (File)
Oct 13 2023, 5:10 AM
Unknown Object (File)
Oct 9 2023, 10:35 AM
Unknown Object (File)
Sep 26 2023, 11:23 AM
Unknown Object (File)
Sep 26 2023, 11:22 AM
Unknown Object (File)
Sep 26 2023, 11:20 AM
Unknown Object (File)
Sep 7 2023, 1:39 PM



This version brings a lot of changes, breaks the ABI, and changes the structure of the libraries.


Test Plan

To be testes with all Tox clients:


Diff Detail

rP FreeBSD ports repository
Lint Not Applicable
Tests Not Applicable

Event Timeline

All of them fail.
qTox fails with this error message:

-- Checking for one of the modules 'libtoxav'
CMake Error at cmake/Dependencies.cmake:73 (message):
  TOXAV package, library or framework not found

You need to tell them. I saw that they were saying that they will release toxcore once qTox works with it.

In D14558#305456, @yuri wrote:

All of them fail.

Yes, of course, this is why I did not upgrade net-im/tox but submitted this on phabricator!
We have to wait for updates of the clients and synchronize them.
E.g., toxic released a new version today: see

I've just submitted a PR, it will be easier to coordinate the different ports:

net-im/py-toxcore-c: r463518 makes it compatible with toxcore 0.2.0

net-im/qTox: r463597 makes it compatible with toxcore 0.2.0

Labeling it as "accepted" since the other 2 ports aren't maintained by me.

This revision is now accepted and ready to land.Mar 4 2018, 7:46 PM

Thanks Yuri!
Toxic is also ready, we are just waiting for

There are many .so removed. If there are any port that link with them, you need to bump them so that they get rebuilt.

There is a disagreement in uTox
One influential project member doesn't trust the TokTok/c-toxcore version.
Otherwise, the patch is ready there since Dec 30, 2017.

I think you should branch out net-im/tox12, keep uTox on it, and commit the new tox-0.2.0.
Otherwise there could be months until this is resolved.

This revision was automatically updated to reflect the committed changes.