Using custom ebuilds

Not every package has an ebuild in the Gentoo or GURU repositories, so it may be needed to add custom packages or extra repositories to Florist.

Utilizing the Gardenhouse ebuilds directory

This depends on how Gardenhouse is used:

Used from a florist git clone

If Florist is being used directly from the git repo (i.e. it was not specifically installed), then any custom ebuild can be placed inside the Florist ebuilds/ directory. It is copied directly into the rootfs as part of the Gardenhouse repository and can be accessed like any other package.

Used through a Florist package

If Florist was installed as a system package, it is possible to simply place the ebuilds in the root of the custom overlay like one would in any other Gentoo overlay. During the build, the name of the overlay will be accessible as the name of the directory the overlay files are in (i.e. if the overlay files are in tmp/my_overlay, the overlay will be called my_overlay during the build.

Using a custom Gentoo overlay

If the package exists in some Gentoo overlay already, it can be added through a file extra in <overlay>/extras/<profile>/etc/portage/repos.conf/repo.conf

{.config path="<overlay>/extras/<profile>/etc/portage/repos.conf/steam-overlay.conf" title="Adding the steam-overlay repository" [steam-overlay] location = /var/db/repos/steam-overlay sync-type = git sync-uri = https://github.com/anyc/steam-overlay.git