Creating Your Own Overlay

This page intends to get your local overlay going.

   Note

With current versions of app-admin/ego the directory /etc/portage/repos.conf/ is no longer a symbolic link, therefore old workarounds are not needed anymore.

Creating the overlay

We will use /var/git/overlay as primary location directory for the overlay. The location can be anywhere on your system, below is an example location tied with /var/git/, is where regular tree located too.

root # mkdir /var/git/overlay

   Important

Do not store your overlay inside of /var/git/meta-repo. If you do it will get erased when you run ego sync.

Clone the skeleton overlay from github. Change the repository's name from skeleton to a name as it will appear when emerging. Here we use myoverlayname as an example, choose your name accordingly.

root # cd /var/git/overlay
root # git clone  https://github.com/funtoo/skeleton-overlay.git myoverlayname

Configure the overlay

We will enable portage settings required for the overlay to be functional.

root # echo "myoverlayname" > /var/git/overlay/myoverlayname/profiles/repo_name

   /etc/portage/repos.conf/myoverlayname.conf - Add your overlay to portage

[myoverlayname]
location = /var/git/overlay/myoverlayname
auto-sync = no
priority = 10

   Tip

The priority key is needed to ensure that your overlay has higher priority to the kit's overlays, which are default priority 1

This would be starting point for your own overlay. You are ready to add new ebuilds that are not present in portage tree or fix the ebuilds from portage tree you are not satisfied with, updating old packages or removing newer package versions.

   Note

equery may print this warning on execution:

user $ equery u gcc
Unavailable repository 'gentoo' referenced by masters entry in '/var/git/myoverlayname/metadata/layout.conf'
...

This is a known equery bug, but should not cause any adverse effects.