From 58fc2cc617d0b83eb425fc9e1790d4a1ca8f1ea4 Mon Sep 17 00:00:00 2001 From: Konstantin Kharlamov Date: Sun, 11 Feb 2024 00:21:38 +0300 Subject: [PATCH 1/3] package.json: add `pkg` to the dev-deps This is used for building purposes, so let's enlist it explicitly --- package.json | 3 +++ 1 file changed, 3 insertions(+) diff --git a/package.json b/package.json index db317752..ff0c2d89 100644 --- a/package.json +++ b/package.json @@ -32,6 +32,9 @@ "which": "^4.0.0", "yargs": "^17.0.0" }, + "devDependencies": { + "pkg": "^5.0.0" + }, "files": [ "cmds", "src", From 34b31faa2a500b4641a7cba4e82349f0f88e7c81 Mon Sep 17 00:00:00 2001 From: Konstantin Kharlamov Date: Sat, 10 Feb 2024 16:46:12 +0300 Subject: [PATCH 2/3] docs: add PKGBUILD and installation instructions for Archlinux Fixes: https://github.com/emacs-eask/cli/issues/215 --- PKGBUILD | 19 +++++++++++++++++++ .../Getting-Started/Install-Eask/_index.en.md | 11 ++++++++++- 2 files changed, 29 insertions(+), 1 deletion(-) create mode 100644 PKGBUILD diff --git a/PKGBUILD b/PKGBUILD new file mode 100644 index 00000000..07256da8 --- /dev/null +++ b/PKGBUILD @@ -0,0 +1,19 @@ +pkgname='eask' +pkgver=$(git tag --sort=-creatordate | head -n1).$(git rev-parse --short HEAD) +pkgrel=1 +pkgdesc='CLI for building, running, testing, and managing your Emacs Lisp dependencies' +arch=('x86_64') +makedepends=('npm') +url='https://github.com/emacs-eask/cli' +license=('GPL-3.0') + +prepare() { + npm i + npm run pkg-linux-x64 +} + +package() { + mkdir -p "$pkgdir/usr/bin" + # ATM eask only works when `lisp` dir is installed together with the binary + cp -r "${startdir}/lisp" "${startdir}/dist/eask" "$pkgdir/usr/bin" +} diff --git a/docs/content/Getting-Started/Install-Eask/_index.en.md b/docs/content/Getting-Started/Install-Eask/_index.en.md index 05c3eb56..6132a424 100644 --- a/docs/content/Getting-Started/Install-Eask/_index.en.md +++ b/docs/content/Getting-Started/Install-Eask/_index.en.md @@ -90,6 +90,15 @@ automatically updated. $ sudo snap install eask-cli ``` +### 📦 Arch (Linux) + +There's a `PKGBUILD` that builds `eask` from sources and creates a package, so +inside the top directory of the repository you can simply run: + +```sh +$ makepkg -i +``` + ### 📦 Chocolatey (Windows) If you have [Chocolatey](https://chocolatey.org/) installed on your machine, you can @@ -150,7 +159,7 @@ On Windows, set PATH=%PATH%;c:/path/to/eask/bin ``` -Once you have set it up correctly, try `eask --version` then you should see +Once you have set it up correctly, try `eask --version` then you should see the current eask's version number! 🎉 🎊 From f069b46ab419256da1fe6c255d72e9105618c20c Mon Sep 17 00:00:00 2001 From: Konstantin Kharlamov Date: Sat, 10 Feb 2024 16:49:57 +0300 Subject: [PATCH 3/3] docs: mention in "build from source" the building part --- docs/content/Getting-Started/Install-Eask/_index.en.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/content/Getting-Started/Install-Eask/_index.en.md b/docs/content/Getting-Started/Install-Eask/_index.en.md index 6132a424..0868a297 100644 --- a/docs/content/Getting-Started/Install-Eask/_index.en.md +++ b/docs/content/Getting-Started/Install-Eask/_index.en.md @@ -141,6 +141,8 @@ $ cd eask-cli # install the requirements $ npm install +# build from sources. For available targets see `scripts` in `package.json` +$ npm run pkg-linux-x64 ``` ### 🏡 Setup