Bug 601038 – net-libs/tox - move to TokTok/c-toxcore FORK

• Product: Gentoo Linux
• Status: RESOLVED FIXED

[Description Alex Acevedo 2016-11-27 23:53:33 UTC]

As stated on https://tox.chat:

TokTok/c-toxcore is a fork of the original irungentoo/toxcore. Toxcore developer, irungentoo, has been very busy lately and unable to find time to work on Toxcore. Because any change to Toxcore should be first reviewed and approved by irungentoo, as he is the only one who can merge changes, Toxcore development has been stalled for some time now. To get around this, a non-hostile Toxcore fork was created where the development is currently ongoing.


Several Tox clients have already rebased to c-toxcore, and it's been acknowledged by the site itself as a non-hostile fork representing a maintained "upstream" until irungentoo is able to return. I would like to suggest that the Gentoo acknowledge this development and rebase the git ebuild to upstream while providing a new ebuild for the latest release from c-toxcore.

Github: https://github.com/TokTok/c-toxcore

Current Release: https://github.com/TokTok/c-toxcore/releases/tag/v0.0.5

[Comment 1 Alex Acevedo 2016-11-28 00:01:10 UTC]

I almost forgot, TokTok also represents a new project implementing Tox and several wrappers at the moment, and not necessarily just a single user's fork:

TokTok Project Homepage: https://toktok.github.io/

[Comment 2 Zetok 2016-12-04 20:57:41 UTC]

(In reply to Alex Acevedo from comment #0)
> As stated on https://tox.chat:
> 
> TokTok/c-toxcore is a fork of the original irungentoo/toxcore. Toxcore
> developer, irungentoo, has been very busy lately and unable to find time to
> work on Toxcore. Because any change to Toxcore should be first reviewed and
> approved by irungentoo, as he is the only one who can merge changes, Toxcore
> development has been stalled for some time now. To get around this, a
> non-hostile Toxcore fork was created where the development is currently
> ongoing.
> 
> 
> Several Tox clients have already rebased to c-toxcore, and it's been
> acknowledged by the site itself as a non-hostile fork representing a
> maintained "upstream" until irungentoo is able to return. I would like to
> suggest that the Gentoo acknowledge this development and rebase the git
> ebuild to upstream while providing a new ebuild for the latest release from
> c-toxcore.
> 
> Github: https://github.com/TokTok/c-toxcore
> 
> Current Release: https://github.com/TokTok/c-toxcore/releases/tag/v0.0.5

A small correction: none of Tox clients present in Gentoo support c-toxcore yet, since its API changed and there have not been any stable release yet.

AFAIK out of desktop clients only µTox so far has switched to c-toxcore, but it's not in the tree.

c-toxcore's first ~stable release (v0.1.0) is planned on 12.09[1], and that's what is planned to be targeted by qTox and Toxic (Tox clients in Gentoo).

Given that c-toxcore changed API to something that neither client has support for in their `master` or releases, there's no reason to have in Gentoo support for it yet.

I don't plan to write/maintain ebuilds for current unstable c-toxcore releases (like v0.0.5), with an exception of live ebuild.

I'll start working on adding slots to ebuilds. After stable release I'll add the ebuild for new ~stable release and switch live ebuild to TokTok.


[1] https://github.com/TokTok/c-toxcore/milestone/8

[Comment 3 Zetok 2016-12-19 20:31:16 UTC]

Done in https://github.com/gentoo/gentoo/commit/020e03cf1cf0f62fda22961b306b81e2e0daacf0, thus closing.