Skip to content
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

check if double-build is still necessary for Linux #18

Closed
7 tasks done
conradkleinespel opened this issue May 11, 2017 · 1 comment
Closed
7 tasks done

check if double-build is still necessary for Linux #18

conradkleinespel opened this issue May 11, 2017 · 1 comment
Assignees

Comments

@conradkleinespel
Copy link
Owner

conradkleinespel commented May 11, 2017

The current Rooster installers build the code both in release and debug modes, because there used to be a bug in the clipboard library on Linux. This bug has been resolved. So as to speed up install times, we shall build only in release mode.

Tasks:

  • clone the Git repository for Rooster: git clone https://github.com/conradkdotcom/rooster.git
  • build and run Rooster in release mode (ie cargo build --release)
  • add a password: ROOSTER_FILE=/tmp/test.rooster rooster add test test
  • retrieve the password: rooster get test
  • paste the password somewhere to see if the clipboard copy works as expected
  • if clipboard works, replace debug binary with the release binary (see the way we do for the rooster binary)
  • add yourself to the contributors' list in README.md in alphabetical order

If you have any questions, just let us know and we'll jump in to help.

@conradkleinespel
Copy link
Owner Author

done

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant