Add PKGBUILD to repository, fix untrue statement in README

This commit is contained in:
Lucien Cartier-Tilet 2020-08-11 19:01:15 +02:00
parent 4e2acb9682
commit e1e70d9d7f
Signed by: phundrak
GPG Key ID: BD7789E705CB8DCA
3 changed files with 55 additions and 3 deletions

2
.gitignore vendored
View File

@ -1 +1,3 @@
/target /target
/pkg/
/src/pumopm-git/

40
PKGBUILD Normal file
View File

@ -0,0 +1,40 @@
# Maintainer: Lucien Cartier-Tilet <lucien@phundrak.com>
pkgname=pumopm-git
pkgver=.r0.4e2acb9
pkgrel=1
pkgdesc="A tiny power manager written in Rust"
arch=('i686' 'x86_64' 'arm' 'armv6h' 'armv7h' 'aarch64')
url="https://labs.phundrak.com/phundrak/pumopm"
license=('GPL3')
depends=()
makedepends=('rustup' 'git')
options=()
source=("$pkgname::git+https://github.com/phundrak/pumopm")
md5sums=('SKIP')
pkgver() {
cd "$pkgname"
local tag=$(git tag --sort=-v:refname | grep '^[0-9]' | head -1)
local commits_since=$(git rev-list $tag..HEAD --count)
echo "$tag.r$commits_since.$(git log --pretty=format:'%h' -n 1)"
}
build() {
cd "$pkgname"
if command -v rustup >/dev/null 2>&1; then
RUSTFLAGS="-C target-cpu=native" rustup run stable cargo build --release
elif rustc --version | grep -q stable; then
RUSTFLAGS="-C target-cpu=native" cargo build --release
else
cargo build --release
fi
}
package() {
cd "$pkgname"
install -Dm755 "target/release/pumopm" "$pkgdir/usr/bin/pumopm"
install -Dm644 "LICENSE" "$pkgdir/usr/share/licenses/${pkgname}/LICENSE"
}
# vim:set ts=2 sw=2 et:

View File

@ -40,6 +40,16 @@
$ cargo install --path . # optional, to install for the user the project $ cargo install --path . # optional, to install for the user the project
#+END_SRC #+END_SRC
If you are an Arch Linux user, make sure you have ~rustup~ installed, and then
you can install PumoPM using the ~PKGBUILD~ available in the repository. To do
so, simply run
#+BEGIN_SRC sh
$ makepkg -si
#+END_SRC
You will then have PumoPM installed as a native package on your machine which
you can uninstall using Pacman.
* Usage * Usage
It is possible to run PumoPM with a couple of different flags. You will find It is possible to run PumoPM with a couple of different flags. You will find
their description here: their description here:
@ -50,9 +60,9 @@
- ~-c --critical~ :: level at which the battery is considered to be critical - ~-c --critical~ :: level at which the battery is considered to be critical
- ~-r --refresh-rate~ :: refresh rate of the batterys reads - ~-r --refresh-rate~ :: refresh rate of the batterys reads
- ~-v --verbose~ :: augment the programs verbosity, can be repeated - ~-v --verbose~ :: augment the programs verbosity, can be repeated
The arguments ~-l~, ~-L~ and ~-c~ accept an integer between 5 and 75 (actually The arguments ~-l~, ~-L~ and ~-c~ accept an integer between 5 and 95 (actually
any value that will fit in an unsigned byte, but it will be rounded up to 5 or any value that will fit in an unsigned byte, but it will be rounded up to 5 or
down to 75), while ~-r~ accepts any integer that can fit in a ~u64~, although down to 95), while ~-r~ accepts any integer that can fit in a ~u64~, although
Im sure youll never need that long of a refresh time. Im sure youll never need that long of a refresh time.
The levels will also see their values ordered. If the ~-L~ value is higher The levels will also see their values ordered. If the ~-L~ value is higher