Ebuild repository/ko

Within Gentoo Linux, users already have one "main" package repository, in the past synonymously referred to as the "Portage tree", although this term should be phased out since package managers other than Portage can interact with package repositories in Gentoo. The main repository contains all the software packages (called ebuilds) maintained by Gentoo developers. Users can add additional repositories to the tree that are "layed over" the main tree - hence the name, overlays.

Since package repositories are nothing more (or less) than a set of files (ebuilds, metadata files, ChangeLog entries ...) these repositories can be pulled in from public repositories (git, cvs, svn ...) or downloaded as tarballs and extracted manually onto the system. It is advised to use managed repositories by trusted third parties; any installed overlay will cause Portage to look through the overlayed files when deciding which software to install. If compromised code is in the overlay, then compromised packages could be installed on the system.

Repositories
Additional package trees are usually hosted by repositories. These are overlays that are ready to be incorporated on Gentoo systems. The now default approach for handling repositories is through which, like many other Portage related locations, can be a directory as well.

A deprecated, yet still supported method is to use the  variable inside. This variable can point to one or more additional locations on the file system where repositories are available. The use of the directory is highly preferred.

Repository definitions inside also inform Portage if and how the repository can be updated. With it, calling emerge --sync will automatically update the repositories as well.

For more information, see /etc/portage/repos.conf and the Portage/Sync article.

오버레이 우선순위
각각의 오버레이에는 유일의 우선순위가 있습니다. 여러 오버레이에 특정 버전을 발견했을 경우 확인하며, 해결 방법은 혼란스럽지 않습니다. 높은 우선순위를 지닌 오버레이의 이빌드는 낮은 우선순위를 가진 오버레이의 이빌드보다 우선합니다.

우선순위가 붙은 오버레이 목록은 다음 목록 출력으로 볼 수 있습니다.

The default Gentoo Portage tree will have a priority of -1000. That means that all other overlays generally take precedence as they are assigned a higher priority. That is the default behavior, because overlays are designed to "lay over/on top" of the portage tree.

Supporting tools
A number of tools support or integrate with overlays.

Layman
The layman application makes it easier to manage and update multiple additional overlays. It is a command-line application through which publicly available overlays can be listed, subscribed to and unsubscribed from, as well as update those repositories.

It supports both the as well as  method.
 * When using the method, layman manages a dedicated configuration file which should be sourced in by
 * When using, layman manages the file directly

여러가지 오버레이를 단순하게 관리하기 위해 layman이라는 도구를 개발했습니다. 이 도구는 사용자와 개발자가 관리하는 오버레이를 알아내며  위치에 오버레이를 추가하여 설치하고 동기화 할 수 있게 합니다.

emaint
See Project:Portage/Sync and man 1 emaint.

eix 통합
eix-sync is a wrapper starting emerge --sync (which in turn starts emaint sync --auto) followed by eix-update. For further details see the Eix article and man 1 eix.

캐시 만들기
거대 오버레이를 설치하면, 포티지에서 의존성 확인과 같은 작업을 처리하는데 오랜 시간이 걸릴 수 있습니다. 보통 오버레이가 메타데이터 캐시를 보유하고 있지 않기 때문입니다.

Generate a local metadata cache by running emerge --regen</tt> after syncing the overlays:

Be careful, because emerge --regen</tt> takes a lot of time and it's not recommended for rsync users as rsync updates the cache using server-side caches (most of users of portage are rsync users). Rsync users should simply run emerge --sync</tt> (or eix-sync</tt>) to regenerate the cache. It's probably only users of very large overlays should try emerge --regen</tt>.

안전하지 않은 오버레이 활용
알 수 없는 저질의 큰 규모의 오버레이를 활용한다면 전체 오버레이에 강 마스크를 지정하는 것이 좋은 방법입니다.

After that unmask the packages that will be installed.

External resources

 * https://overlays.gentoo.org