-
Notifications
You must be signed in to change notification settings - Fork 3
Installation
If you're using another distribution, inary can be used in two ways
- to completely switch to sulin: with inary it's easy to switch to sulin without downloading and reinstalling iso
- to install programs in your userspace: Like brew package manager
sh ~# git clone https://github.com/SulinOS/inary.git
sh ~# cd inary
sh ~# python3 setup.py install
sh ~# cd ..
sh ~# git clone https://github.com/SulinOS/switch-sulin.git
sh ~# cd switch-sulin
sh ~# ./switch-sulin --interactive
sh ~# inary rdb
sh ~# inary cp
sh ~# shutdown -r now
sh ~$ mkdir ~/.inary
sh ~$ git clone https://github.com/SulinOS/inary.git
sh ~$ python3 setup.py build
sh ~$ python3 setup.py install --root=~/.inary
sh ~$ python3 scripts/inary-profile select brew-like
sh ~$ inary rdb
In the distribution of Sulin, Inary comes preloaded.
::: {.note} ::: {.admonition-title} Note :::
you can install inary fallowing steps to installing any other distro, but this could break the preloaded inary package. :::
Inary allows self-updating...
sh ~$ inary ur
sh ~$ inary up inary
...or you can also upgrade it from exist cloned repository
sh ~# cd inary
sh ~# git pull
sh ~# python3 setup.py install
For inary package management system, Comar has been forked and developed and scom is a former inary dependency and contains pisi package configuration scripts.
Unless otherwise specified (scom script running can be ignored with using [--ignore-scom]{.title-ref} parameter), scom scripts will be executed after package installation.
However, unlike in the past, existing inary allows packet processing without using scom. In this case, the configuration after the installation of the packages is left entirely to the users hand.