ttyper icon indicating copy to clipboard operation
ttyper copied to clipboard

Add Cargo-less installation methods

Open max-niederman opened this issue 4 years ago • 5 comments

Ideally there should be a way to install on at least some machines without cargo. This will need an installation script to install the language files in lieu of build.rs.

Some alternative installation methods which would be good to include are:

  • sh installation script w/ prebuilt binaries
  • AUR package

For prebuilt binaries, it would be ideal to setup GitHub workflows or similar so that no manual work is needed.

max-niederman avatar Mar 15 '21 23:03 max-niederman

I currently implemented this for my buddy and I's program called lightmon. I used the popular shell program starship as a reference, and how their installation method works is they have a GitHub Action that generates the binaries for all types of platforms automatically whenever you tag a commit, and attaches them to the corresponding GitHub release page. Then, their shell script will just fetch the corresponding binary based on the platform from the release page and install it. Definitely a very clean way to do it, and not hard to do.

reaganmcf avatar May 07 '21 01:05 reaganmcf

There is a ttyper-git package at AUR maintained by me, currently not working because of #25.

dr460nf1r3 avatar May 25 '21 10:05 dr460nf1r3

This is now mostly solved, as pre-built binaries now work out of the box, and binaries are built and uploaded automatically to GitHub releases on every update.

max-niederman avatar Jun 01 '21 22:06 max-niederman

perhaps as binaries are built with Releases, a ttyper-bin package could also be added to the AUR which ships the latest binary release? That seems to be common with many Rust cli utilities on the aur

BachoSeven avatar Nov 06 '21 14:11 BachoSeven

perhaps as binaries are built with Releases, a ttyper-bin package could also be added to the AUR which ships the latest binary release? That seems to be common with many Rust cli utilities on the aur

That would be ideal, but I neither use nor have any experience packaging for Arch, so someone else will probably need to maintain the package.

If anyone's interested in maintaining a package (for any distribution), I'd be happy to integrate it with the existing CI.

max-niederman avatar Nov 09 '21 18:11 max-niederman