The Funtoo Linux project has transitioned to "Hobby Mode" and this wiki is now read-only.
Difference between revisions of "Install/Introducing Portage/ru"
(Updating to match new version of source page) |
(Created page with "Менеджер пакетов Funto Linux под названием Portage имеет команду под названием <code>emerge</code> которая испол...") |
||
Line 6: | Line 6: | ||
{{InstallNavigation|num=12|prev=Configuration Files|next=Kernel}}</noinclude> | {{InstallNavigation|num=12|prev=Configuration Files|next=Kernel}}</noinclude> | ||
Portage | Менеджер пакетов Funto Linux под названием Portage имеет команду под названием <code>emerge</code> которая используется для сборки и установки пакетов из исходных текстов. Также эта команда обеспечивает контроль за всеми зависимостями этих пакетов. Запустить emerge можно следующим образом: | ||
{{console|body= | {{console|body= |
Revision as of 23:28, April 13, 2019
Руководство по установке: Введение в Portage
Install Guide, Chapter 12 | < Prev | Next > |
Менеджер пакетов Funto Linux под названием Portage имеет команду под названием emerge
которая используется для сборки и установки пакетов из исходных текстов. Также эта команда обеспечивает контроль за всеми зависимостями этих пакетов. Запустить emerge можно следующим образом:
(chroot) # emerge packagename
When you install a package by specifying its name in the command-line, Portage records its name in the /var/lib/portage/world
file. It does so because it assumes that, since you have installed it by name, you want to consider it part of your system and want to keep the package updated in the future. This is a handy feature, since when packages are being added to the world
set, we can update our entire system by typing:
(chroot) # ego sync (chroot) # emerge -auDN @world
This is the "official" way to update your Funtoo Linux system. Above, we first update our Portage tree using git to grab the latest ebuilds (scripts), and then run an emerge command to update the world
set of packages. The options specified tell emerge
to:
a
- show us what will be emerged, and ask us if we want to proceedu
- update the packages we specify -- don't emerge them again if they are already emerged.D
- Consider the entire dependency tree of packages when looking for updates. In other words, do a deep update.N
- Update any packages that have changed (new) USE settings.
You should also consider passing --with-bdeps=y
when emerging @world, at least once in a while. This will update build dependencies as well.
Of course, sometimes we want to install a package but not add it to the world
file. This is often done because you only want the package installed temporarily or because you know the package in question is a dependency of another package. If this behavior is desired, you call emerge like this:
(chroot) # emerge -1 packagename
Advanced users may be interested in the Emerge wiki page.
Updating World
Certain packages in the Funtoo stage3 tarball are compiled with the bindist USE flag enabled by default. (The bindist flag controls enabling or disabling of options for proprietary and/or patented parts of code which is not allowed to be distributed in images due to licensing issues). You may notice a dependency resolution problem with bindist USE flags during updating packages after initial system setup. To avoid potential problems, update the system before first boot or any other package installation as shown below:
(chroot) # ego sync (chroot) # emerge -auDN @world
Make sure you read any post emerge messages and follow their instructions. This is especially true if you have upgraded perl or python.
If you choose different file systems then the ones in this guide, like JFS, XFS, ZFS or Btrfs, make sure the kernel has the tools to check them. For JFS the package is jsfutils, similar packages exist for all file systems.