diff options
author | Silvio Rhatto <rhatto@riseup.net> | 2017-09-18 19:30:27 -0300 |
---|---|---|
committer | Silvio Rhatto <rhatto@riseup.net> | 2017-09-18 19:30:27 -0300 |
commit | 41c08b4aeac22d5d44269646773ad6d3b237ed5f (patch) | |
tree | 0203471aabaa30694c9f8e306f6309c0ca61676a | |
parent | 3655a4da32e12a627ad34aa6711f841843b212a2 (diff) | |
download | stowpkg-41c08b4aeac22d5d44269646773ad6d3b237ed5f.tar.gz stowpkg-41c08b4aeac22d5d44269646773ad6d3b237ed5f.tar.bz2 |
Updates README
-rw-r--r-- | README.md | 66 | ||||
-rwxr-xr-x | stowpkg | 8 |
2 files changed, 32 insertions, 42 deletions
@@ -12,12 +12,6 @@ Features * Repository signature verification using GnuPG and signed git commits. * Small enough so everybody can learn how a package manager works. -Coming features ---------------- - -* Automatic application patching. -* Source code verification using multiple methods (commit hash, checksums, OpenPGP). - Installation ------------ @@ -41,56 +35,29 @@ Usage stowpkg install <package> # install packages from source stowpkg build # simple package builder (./configure && make && make install) -Coming usage ------------- - - stowpkg list # list packages installed - stowpkg remove <package> # remove packages - stowpkg purge <package> # purge packages - stowpkg update # update ports repository - stowpkg upgrade [package] # upgrade packages - stowpkg upstream <package> # check packages versions at upstream - Running installed applications ------------------------------ Make sure to include stowpkg package tree into your `PATH`, `MANPATH`, `LD_LIBRARY_PATH`, etc. -Params ------- - -Passe using environment variables: - -* `BASE`: defaults `<stowpkg-repo>/tree/<architecture>`, but can be configured to anything like - `/usr/local` with corresponding packages installed `/usr/local/stowpkg`. - Configuration ------------- -Use `~/.config/stowpkg` do put any default parameters. +Use `~/.config/stowpkg` do put any default parameters. Current supported params include -Ports layout ------------- +* `BASE`: defaults to `<stowpkg-repo>/tree/<architecture>`, but can be configured to anything like + `/usr/local` with corresponding packages installed at `/usr/local/stow`. -Check the repo for examples :) - -Repository layout +Filesystem layout ----------------- -Starting from `$BASE` (like `/usr/local`) we have: +Current ports tree is distributed directly along with `stowpkg` source repository. +A binary repository has the following layout starting from `$BASE` (like `/usr/local`): {bin,lib,man,share,etc,src}: usual Unix paths stow package_name-VERSION -Further development -------------------- - -Per-architecture binary package support using git-annex and GnuPG signatures, including: - - stowpkg pack <package> # pack an installed package - stowpkg fetch <package> # fetch package from the repo - What it does ------------ @@ -104,6 +71,27 @@ If you want to do it manually: cd /usr/local/stow/ sudo stow luakit +Further development +------------------- + +* Automatic application patching. +* Source code verification using multiple methods (commit hash, checksums, OpenPGP). + +Other commands can easily be implemented: + + stowpkg list # list packages installed + stowpkg remove <package> # remove packages + stowpkg purge <package> # purge packages + stowpkg update # update ports repository + stowpkg upgrade [package] # upgrade packages + stowpkg upstream <package> # check packages versions at upstream + +Also, per-architecture binary package support might be implemented using +git-annex and GnuPG signatures, giving us commands like + + stowpkg pack <package> # pack an installed package + stowpkg fetch <package> # fetch package from the repo + References ---------- @@ -175,9 +175,11 @@ stowpkg_build () { local package="$1" local version="$2" - # TODO - # Check for package and version - # Otherwise try to guess it + # Check + if [ -z "$version" ]; then + echo "$BASENAME: please specify package name and version" + exit 1 + fi # Set PREFIX if [ -z "$PREFIX" ]; then |