This page intends to get your local overlay going, show how to revision bump a package.
We will use /var/overlay as primary location directory. This directory can be located anywhere, below is an example location.
# mkdir /var/overlayClone the skeleton overlay from github. Change the repository's name from skeleton to a name as it will appear when emerging.
# cd /var/overlay # git clone http://git.funtoo.org/skeleton-overlay/ local && cd local # echo "myoverlayname" > /var/overlay/local/profiles/repo_name # echo "masters = gentoo" >> /var/overlay/local/metadata/layout.conf
[myoverlayname] location = /var/overlay/local masters = gentoo auto-sync = no
Insert portage structure category & package directories. For example, I want to fix apparmor to include the very latest source, you would
mkdir -p /var/overlay/local/sys-apps/apparmor then copy the old ebuild you found online (or on your computer) to the directory.
/var/overlay/local/sys-apps/apparmor/apparmor-2.8.4.ebuild is where the old ebuild would sit. Copy it to the latest upstream version number.
cp apparmor-2.8.4.ebuild apparmor-2.9.2.ebuild then run the ebuild manifest file.
# mkdir -p /var/overlay/local/app-category/package-name # mv package-oldversion.ebuild /var/overlay/local/app-category/package-name/package-oldversion.ebuild # cp /var/overlay/local/app-category/package-name/package-oldversion.ebuild /var/overlay/local/app-category/package-name/package-newversion.ebuild # ebuild *.ebuild manifestfor init files, patches etc: example
# mkdir /var/overlay/local/app-category/package-name/files # nano /var/overlay/local/app-category/package-name/files/package-initYou're ready to emerge the new version, you don't need to sync, you can make minor changes, then emerge, and if it breaks again you can make more minor changes, and emerge again.