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

One step install piranha #377

Open
ketkarameya opened this issue Feb 16, 2023 · 1 comment
Open

One step install piranha #377

ketkarameya opened this issue Feb 16, 2023 · 1 comment

Comments

@ketkarameya
Copy link
Collaborator

ketkarameya commented Feb 16, 2023

This issue tracks the problem (my thoughts, other folk's thoughts) related to making it easy (on-click) :

  1. [Suggested by @conormurray95] For ease of use for other developers it would be more convenient if the binary was available via something like homebrew that could be installed with one command and used via the cli. The reason I have it as a dockerfile right now is so our make flag-cleanup command can be run locally by any dev without any setup because it:
  • Pulls the docker image with Piranha tool installed
  • Mounts our codebase as a volume inside the image
  • Runs the piranha binary against the codebase using whatever flag they input
  1. Release a binary per platform like this - https://github.com/BurntSushi/ripgrep/releases/tag/13.0.0 (go to the bottom of the page to look at the assets)
  2. If folks are ok installing rust up tool chain its actually straightforward. Just cargo install --git https://github.com/uber/piranha.git This will install the polyglot piranha exectuable from the github project This is undocumented. But kinda intuitive for folks familiar with cargo, I will document this.
    • It would be specially nice if we can make a release on crates.io itself. But we have blockers. Crates.io does not accept un verified dependencies. While we have certain modifications to the upstream tree-sitter-grammar repos that we maintain in a branch and are currently under code review . We are waiting for them to accept our changes and make a release.
  3. Some how figure out how to make the perfect pypi release

I think we should do 1, 3 and 4(as much as possible). I would love to do (2) too if we reach a point that we have so many users like ripgrep :)

cc @lazaroclapp


Reference conversations :

#358 (comment)
#311 (comment)

@ketkarameya
Copy link
Collaborator Author

@conormurray95 what is your opinion about option 3? (From your POV)

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

No branches or pull requests

1 participant