-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Still maintained ? #31
Comments
I would suggest using (and contributing to) @carlosefr’s fork instead, since he’s been maintaining it regularly. I have thought of providing a Docker images and CI/CD pipelines for this under @insightfulsystems, but haven’t had the time.
… On 17 Aug 2019, at 12:24, Anders Björklund ***@***.***> wrote:
Is this fork still being maintained, there seems to be no updates since 2017.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
It seems that Carlos fork has been abandoned, while there are some new versions available upstream (1.2.76 --> 1.2.79) So I guess this as good as any, with the suggested patch it compiles and runs. Maybe will add the patches from dbmx.net |
Indeed I stopped considering Kyoto Tycoon as something I'd consider using in future projects so I decided to archive my fork (many of the later changes were already just me using it as a testbed for some experiment, like selinux policies, because of its relative simplicity). I'd already moved on from trying to get PRs merged into this repo since 2017. My fork still looks like the most "current" version, though. The new upstream Kyoto Cabinet versions don't seem to contain some fixes I've added/collected since 2012 (and there are no new upstream versions of Kyoto Tycoon). I'm not sure how/where KT/KC is still being used in the wild, so may years after its last significant changes. |
The last "situation summary" I found is https://charlesleifer.com/blog/kyoto-tycoon-in-2019/ which sums it up pretty neatly. Maybe eventually the new database "Tkrzw" will grow a new remote, but at the moment KT looks more or less abandoned... |
Is this fork still being maintained, there seems to be no updates since 2017.
The text was updated successfully, but these errors were encountered: