Ebuild guidance for ecosystems

Gentoo developers have created tools and guides to handle packaging software for certain ecosystems which follow a different format or require special steps. This article provides guidance for creating ebuilds in an unfamiliar ecosystem.

Table

Language	Tools	Notes	Links
Python	app-portage/gpyutils gs-pypi (more for quick installs rather than for submitting to ::gentoo)	Package names should follow pypi Remember to unpin any dependencies where possible	Gentoo Python Guide
Perl	dev-perl/Gentoo-PerlMod-Version app-portage/g-cpan (more for quick installs rather than for submitting to ::gentoo)	Make sure the correct version is used from gentoo-perlmod-version.pl	How to version bump dev-perl
Go	dev-go/go-licenses bump-go	N/A	Go ebuild tricks Writing go Ebuilds
Rust	app-portage/pycargoebuild dev-util/cargo-ebuild dev-util/cargo-license	Often need to set environment variables to use system copies of libraries, bug #709568	Writing Rust ebuilds
Java	Java-ebuilder	N/A	Gentoo Java Packing Policy Java Developer Guide
Haskell	app-portage/hackport	N/A	N/A

See also

• User:Sam/Useful scripts