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. Additional package trees are usually hosted by repositories. Users can add such additional repositories to the tree that are "laid over" the main tree - hence the name, overlays.

저장소
Package repositories are nothing more (or less) than a set of files (ebuilds, metadata files, ChangeLog entries ...). These 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 overlaid files when deciding which software to install. If compromised code is in the overlay, then compromised packages could be installed on the system.

The now default approach for handling repositories is through which, like many other Portage related locations, can be a directory as well.

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

A deprecated, yet still supported method is to use the PORTDIR_OVERLAY 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.

더 많은 정보는 /etc/portage/repos.conf와 Portage/Sync article 게시글을 참고하십시오.

우선순위
Each overlay has its unique priority. This makes sure that in the case of a specific version being found in several overlays, the resolution is unambiguous. Ebuilds from overlays with higher priority numbers (for example 60) take precedence over ebuilds from overlays with lower priorities (such as 50).

The list of overlays with their priorities can be obtained through the output of the following commands (look for the "Repositories" string):

기본 젠투 포티지 트리는 -1000 우선순위를 갖습니다. 이는 다른 오버레이에 보통 할당하는 우선순위보다 훨씬 높은 우선순위를 배당한다는 의미입니다. 오버레이를 포티지 트리 "위에 눕혀놓은" 방식으로 설계했기 때문에 이런 동작은 기본입니다.

지원 도구
오버레이를 지원하거나 오버레이에 붙는 도구는 여러가지가 있습니다.

Layman
The 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,  manages a dedicated configuration file which should be sourced in by
 * When using, manages the  file directly

더 많은 정보는 Laymanen 과 Layman 설정en 을 참고하십시오

emaint
See Project:Portage/Sync and.

eix
is a wrapper starting (which in turn starts ) followed by. For further details see the Eix article and.

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

Generate a local metadata cache by running after syncing the overlays:

Be careful, because 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 (or ) to regenerate the cache. It's probably only users of very large overlays should try.

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

그 다음 설치할 꾸러미의 마스크를 해제하십시오.

추가 참조

 * Project:Overlaysen - 오버레이 지원 공식 젠투 프로젝트.
 * Project:Overlays/User_Guideen - 오버레이 프로젝트에서 작성한 사용자 안내서.
 * 젠투 오버레이 개발자 안내서en

외부 자료

 * https://overlays.gentoo.org
 * https://github.com/gentoo/