Created attachment 421674 [details] keybase-1.0.7.0.ebuild The Keybase.io client has apparently been rewritten in Go. The version of Keybase presently in the tree (app-crypt/keybase-0.8.25) was written in Node.js. The ebuild in the tree, therefore, no longer applies to the present release. Attached is a new ebuild that builds the new Keybase.io client using >=dev-lang/go-1.5. I have tested the resulting binary lightly. (It runs and appears to function, but I do not yet have a Keybase login, so I can't fully test it.)
Is this logically a different package than app-crypt/keybase? (I'm wondering about the apparent package rename.) Also, I'm wondering about all those extra words in the title now. My ebuild only builds the command-line client (which includes the service), not the iOS, Android, or Electron apps. I guess maybe this ebuild would work on OS X. (Does Gentoo support OS X?)
(In reply to Matt Whitlock from comment #1) > Is this logically a different package than app-crypt/keybase? (I'm wondering > about the apparent package rename.) > I am not sure. From reading through the project's descriptions it sounds to me as if app-crypt/keybase is the CLI. But then again, the Go code you refer to supposedly also includes a CLI client. Do you know what the difference is between these two projects (client and node-client)?
(In reply to Nicolas Bock from comment #2) > (In reply to Matt Whitlock from comment #1) > > Is this logically a different package than app-crypt/keybase? (I'm wondering > > about the apparent package rename.) > > > I am not sure. From reading through the project's descriptions it sounds to > me as if app-crypt/keybase is the CLI. But then again, the Go code you refer > to supposedly also includes a CLI client. Do you know what the difference is > between these two projects (client and node-client)? As luck would have it, I stumbled upon a bug report showing some output from an older version of the CLI client. https://github.com/keybase/keybase-issues/issues/1712 The first comment in that bug report shows the output from "keybase version", showing Keybase CLI version 0.8.15 (which is in the range of versions of app-crypt/keybase in the Portage tree) and a Node.js version, suggesting that the Keybase CLI was once written in Node.js. Now the Keybase CLI is written in Go. In other words, if you really want to change the name of the package to app-crypt/keybase-client, then you should enter a package move.
(In reply to Matt Whitlock from comment #3) > (In reply to Nicolas Bock from comment #2) > > (In reply to Matt Whitlock from comment #1) > > > Is this logically a different package than app-crypt/keybase? (I'm wondering > > > about the apparent package rename.) > > > > > I am not sure. From reading through the project's descriptions it sounds to > > me as if app-crypt/keybase is the CLI. But then again, the Go code you refer > > to supposedly also includes a CLI client. Do you know what the difference is > > between these two projects (client and node-client)? > > As luck would have it, I stumbled upon a bug report showing some output from > an older version of the CLI client. > > https://github.com/keybase/keybase-issues/issues/1712 > > The first comment in that bug report shows the output from "keybase > version", showing Keybase CLI version 0.8.15 (which is in the range of > versions of app-crypt/keybase in the Portage tree) and a Node.js version, > suggesting that the Keybase CLI was once written in Node.js. > > Now the Keybase CLI is written in Go. > > In other words, if you really want to change the name of the package to > app-crypt/keybase-client, then you should enter a package move. There are two repositories under keybase on github: node and node-client. The node-client is the js based code, node is many things including a CLI client. Are you suggesting that the node-client project is being phased out in favor of the node project?
(In reply to Nicolas Bock from comment #4) > There are two repositories under keybase on github: node and node-client. > The node-client is the js based code, node is many things including a CLI > client. Are you suggesting that the node-client project is being phased out > in favor of the node project? There is no "keybase/node" repository on Github. There is "keybase/client" and "keybase/node-client". The "node-client" is the older one; last commit was on 30 November 2015. The "client" repository is the newer one; last commit was today. Further, the right-hand column at https://keybase.io/download says: > Deprecation warning Node.js users, please uninstall with: > > npm uninstall -g keybase > > Source code > > Keybase is open source. You can always find our latest source code at > https://github.com/keybase/client. So the Node.js client has been deprecated, and the new client is in the "client" repository.
(In reply to Matt Whitlock from comment #5) > (In reply to Nicolas Bock from comment #4) > > There are two repositories under keybase on github: node and node-client. > > The node-client is the js based code, node is many things including a CLI > > client. Are you suggesting that the node-client project is being phased out > > in favor of the node project? > > There is no "keybase/node" repository on Github. There is "keybase/client" > and "keybase/node-client". The "node-client" is the older one; last commit > was on 30 November 2015. The "client" repository is the newer one; last > commit was today. Further, the right-hand column at > https://keybase.io/download says: > > > Deprecation warning Node.js users, please uninstall with: > > > > npm uninstall -g keybase > > > > Source code > > > > Keybase is open source. You can always find our latest source code at > > https://github.com/keybase/client. > > So the Node.js client has been deprecated, and the new client is in the > "client" repository. Cool! Thanks for the additional information!
Incidentally, I now have a Keybase account, and I've successfully used the Keybase CLI built by the attached ebuild to sign in, attach a PGP key, and prove my identity on several services, so I'd declare that it works correctly. Would you change the package name in the title of this ticket back to "app-crypt/keybase"?
(In reply to Matt Whitlock from comment #7) > Incidentally, I now have a Keybase account, and I've successfully used the > Keybase CLI built by the attached ebuild to sign in, attach a PGP key, and > prove my identity on several services, so I'd declare that it works > correctly. > > Would you change the package name in the title of this ticket back to > "app-crypt/keybase"? I think, given that the current code base is deprecated, we should use the same name. I will have a closer look at your ebuild and update the one in tree.
(In reply to Nicolas Bock from comment #8) > I will have a closer look at your ebuild and update the one in tree. You may want to change my "ln -rs" to a simple "mv" since I don't know if '-r' is available in all deployed versions of 'ln'.
Created attachment 422174 [details] keybase-1.0.7.0.ebuild I omitted a '|| die' in my ebuild, and also I changed the "ln -rs" to a "mv" and used "dirname" in the "mkdir" command.
Renaming the attached ebuild successfully builds keybase-1.0.8.0.
Matt, sorry for the delays, but I finally committed your ebuild to the tree. Please give it a try! And thanks so much for taking the time to writing that ebuild.
(In reply to Nicolas Bock from comment #12) > Please give it a try! Works! Thanks.
