installation.rst 2.2 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677787980
  1. .. -*- coding: utf-8 -*-
  2. %%%%%%%%%%%%%%%%%%%%%
  3. Installation of Inary
  4. %%%%%%%%%%%%%%%%%%%%%
  5. Installation under another distro
  6. `````````````````````````````````
  7. If you're using another distribution, inary can be used in two ways
  8. * to completely switch to sulin: with inary it's easy to switch to sulin without downloading and reinstalling iso
  9. * to install programs in your userspace: Like brew package manager
  10. Use to switch to Sulin from another distro
  11. ------------------------------------------
  12. .. code-block:: shell
  13. sh ~# git clone https://github.com/SulinOS/inary.git
  14. sh ~# cd inary
  15. sh ~# python3 setup.py install
  16. sh ~# cd ..
  17. sh ~# git clone https://github.com/SulinOS/switch-sulin.git
  18. sh ~# cd switch-sulin
  19. sh ~# ./switch-sulin --interactive
  20. sh ~# inary rdb
  21. sh ~# inary cp
  22. sh ~# shutdown -r now
  23. Brew-Like using
  24. ---------------
  25. .. code-block:: shell
  26. sh ~$ mkdir ~/.inary
  27. sh ~$ git clone https://github.com/SulinOS/inary.git
  28. sh ~$ python3 setup.py build
  29. sh ~$ python3 setup.py install --root=~/.inary
  30. sh ~$ python3 scripts/inary-profile select brew-like
  31. sh ~$ inary rdb
  32. Installation on SulinOS
  33. ```````````````````````
  34. In the distribution of Sulin, Inary comes preloaded.
  35. .. note:: you can install inary fallowing steps to installing any other distro, but this could break the preloaded inary package.
  36. Upgrade inary
  37. `````````````
  38. Inary allows self-updating...
  39. .. code-block:: shell
  40. sh ~$ inary ur
  41. sh ~$ inary up inary
  42. ...or you can also upgrade it from exist cloned repository
  43. .. code-block:: shell
  44. sh ~# cd inary
  45. sh ~# git pull
  46. sh ~# python3 setup.py install
  47. Package Post install Processes
  48. ``````````````````````````````
  49. For inary package management system, Comar has been forked and developed and scom \
  50. is a former inary dependency and contains pisi package configuration scripts.
  51. Unless otherwise specified (scom script running can be ignored with using `--ignore-scom` parameter), \
  52. scom scripts will be executed after package installation.
  53. However, unlike in the past, existing inary allows packet processing without using scom. \
  54. In this case, the configuration after the installation of the packages is left entirely \
  55. to the users hand.