vipack became vipak; vipackTree became vipatsar

This commit is contained in:
Norayr Chilingarian 2025-05-29 18:52:58 +04:00
parent 41fe4a7132
commit 8bedfc1689
4 changed files with 24 additions and 24 deletions

View file

@ -1,11 +1,11 @@
![](https://xn--y9azesw6bu.xn--y9a3aq/media/uploads/2022/01/19/4b650ab4-2e97-45f8-8fd3-af1c726399c0.png)
vipack
vipak
======
vipack is a language or dependency agnostic package manager.
vipak is a language or dependency agnostic package manager.
currently it has a backend to retrieve dependencies from the [vipack tree](https://github.com/vishaps/vipackTree).
currently it has a backend to retrieve dependencies from the [vipak tree](https://codeberg.org/vishapoberon/vipatsar).
that is a list of json files, each containing information about the package dependencies, where to download the packages, and how to build those.
@ -14,8 +14,8 @@ build
requirements: git, gmake, cc, voc
`git clone https://github.com/vishaps/vipack`
`cd vipack`
`git clone https://codeberg.org/vishapoberon/vipak`
`cd vipak`
`gmake`
or on freebsd:
@ -25,23 +25,23 @@ or on freebsd:
usage
=====
try `vipack --help`.
try `vipak --help`.
some examples:
`vipack -s` — syncs the default package tree to `~/.vipack/vipackTree`.
`vipak -s` — syncs the default package tree to `~/.vipak/vipatsar`.
`vipack -d -p irc_bot` — only resolves/shows dependencies of the package `irc_bot`, does not download or build packages.
`vipak -d -p irc_bot` — only resolves/shows dependencies of the package `irc_bot`, does not download or build packages.
`vipack -f -p irc_bot` — resolves and fetches required packages.
`vipak -f -p irc_bot` — resolves and fetches required packages.
`vipack -p irc_bot` — will build the package and dependencies in the default prefix: `~/vpkLocal`
`vipak -p irc_bot` — will build the package and dependencies in the default prefix: `~/vpkLocal`
`vipack -a -p irc_bot` — ask for confirmation before building the package and dependencies in the default prefix: `~/vpkLocal`
`vipak -a -p irc_bot` — ask for confirmation before building the package and dependencies in the default prefix: `~/vpkLocal`
`vipack -p irc_bot -P /tmp/coolprefix` — will do the same in the custom prefix.
`vipak -p irc_bot -P /tmp/coolprefix` — will do the same in the custom prefix.
`vipack -p irc_bot -P /tmp/coolprefix -t /tmp/myothertree` — the same, but the dependency resolution will be conducted by using custom package description tree.
`vipak -p irc_bot -P /tmp/coolprefix -t /tmp/myothertree` — the same, but the dependency resolution will be conducted by using custom package description tree.
todo
====