HOWTO make your own Gentoo ebuild
The Gentoo Linux distribution uses simple text-files to describe how software should be installed and configured. These files can be complex and do advanced things but they can also be really simple. Making a basic one is rather easy. This means that there's a lot of custom out-of-tree ebuilds you can (ab)use on Gentoo.
Where to place and how to name custom ebuilds[edit | edit source]
First, make a folder where you will store your own ebuilds.
/usr/local/portage is a good choice.
mkdir -p /usr/local/portage
and set that folder to be an overlay for portage in /etc/make.conf:
The folder structure in your overlay folder should be the same as found in
/usr/portage so if you wanted to make an ebuild for a theme you would put that in
Use the output from
emerge -s package or
emerge -pv package or
eix to find its category and name. These reflect actual folders in /usr/portage. The ebuild for
sys-apps/portage is found in
In what folder you place your own ebuilds is up to you, but it needs to fit one of the portage package categories. An ebuild for a new IM program should be placed in
All patches ebuilds use should be placed in a folder files/ where the ebuild is placed.
The ebuild needs to have a Manifest, a digital signature, for the source files used. These can be made with the command ebuild:
ebuild myebuild-0.1.1.ebuild digest
Once the ebuild is is place and the digital signature is made it can be emerged as usual:
How to make your own ebuilds[edit | edit source]
Take a look at the sample skeleton ebuild file founds on all Gentoo systems.
With very little editing you can use this file to make your own ebuilds.
- Common Ebuild Writing Mistakes - Ebuild Guidelines http://dev.gentoo.org/~liquidx/ebuildmistakes.html
- Gentoo Linux Developers HOWTO http://www.gentoo.org/doc/en/gentoo-howto.xml
- Gentoo Linux Development Policy http://www.gentoo.org/doc/en/policy.xml
- Contributing Ebuilds http://www.gentoo.org/doc/en/ebuild-submit.xml
Using downloaded ebuilds[edit | edit source]
If you download a plain .ebuild file, then copy the file to an appropiate folder in your portage overlay tree and make a digest for it:
mkdir -p /usr/local/portage/app-text/txt2tags cd /usr/local/portage/app-text/txt2tags cp /home/you/txt2tags-1.7.ebuild . ebuild txt2tags-1.7.ebuild digest
Builds from BreakMyGentoo and others come has archives with a Manifest and digest included. Simply extract these files to /usr/local/portage/ and emerge them as usual:
wget http://ebuilds.net/gdesklets-core-0.24.1-rc1.tar.gz tar xfvz gdesklets-core-0.24.1-rc1.tar.gz -C /usr/local/portage/
Where to look for ebuilds[edit | edit source]
- BreakMyGentoo http://www.breakmygentoo.net/
- Gentoo-Portage.com http://gentoo-portage.com/
- Latest Portage Additions http://packages.gentoo.org
Updating ebuilds to new versions[edit | edit source]
If you want to make an ebuild for a new release for slurm, you could:
mkdir -p /usr/local/portage/net-analyzer/slurm cd /usr/local/portage/net-analyzer/slurm cp -r /usr/portage/net-analyzer/slurm ..
Then rename the latest ebuild in portage to your new version
mv slurm-0.2.3.ebuild slurm-0.3.2.ebuild
and use that as the basis for your new ebuild. You could also add -rN to your ebuild to indicate it is a modified version of some ebuild: slurm-0.3.2.ebuild.ebuild becomes slurm-0.3.2.ebuild-r1.ebuild.
Now download the source and make a digital signature:
ebuild slurm-0.3.2.ebuild digest
Now your new ebuild should be available when you do