[ << ] [ < ] [ Home ] [ > ] [ >> ]

Gentoo Developer Handbook

Content:

• Introduction
  This part covers aspects which apply to most areas of Gentoo development. This section is only really relevant if you are a Gentoo developer; otherwise you should skip this.
  1. Introduction
     This section outlines the purpose of the Gentoo Developer Handbook.
  2. Becoming a developer
     This section aims to explain how one can become a Gentoo developer.
  3. What you get
     This section outlines what services are available to Gentoo developers.
  4. Help for new developers
     This section provides help and instructions for new developers.
  5. Developer hierarchy
     This section outlines the hierarchy of Gentoo Developers and development.
• Guides
  This section outlines and explains various development processes and provides standards for Gentoo developers.
  1. Ebuild HOWTO
     This section describes the Gentoo Linux Portage system, how to create new packages for Gentoo, and is also meant to be somewhat of a standard for the Gentoo Developers. It is a work in progress, and is constantly being updated and changed. It is by no means complete. You should always use this in conjunction with the manpages provided by portage (especially ebuild(5)) and the Gentoo Linux Development Policy.
  2. Eclass HOWTO
     This section aims to provide developers with a guide detailing how eclasses work and how they can be applied to ebuilds.
  3. Common ebuild Mistakes
     This section explains the frequent ebuild writing and submission mistakes made by contributors and developers.
  4. Gentoo Metadata
     This section explains the use and need of metadata.xml that is used within the Portage tree.
  5. Ebuild Maintenance HOWTO
     This section describes how developers would perform common tasks when maintaining ebuilds in the Portage tree.
  6. Manifest Signing Guide
     This section describes how developers can sign Manifests in the Portage tree using GPG.
• Policies
  This part covers the different policies which we expect developers to abide when committing items to CVS.
  1. Ebuild policy
     This section outlines the ebuild policy which every ebuild in Portage must follow.
  2. Etiquette policy
     This section outlines the etiquette policy for Gentoo developers.

[ << ] [ < ] [ Home ] [ > ] [ >> ]

The contents of this document are licensed under the Creative Commons - Attribution / Share Alike license.