Gentoo ebuild writing guidelines
E745841
Gentoo ebuild writing guidelines are the official rules and best practices that define how software build scripts (ebuilds) must be written and maintained in the Gentoo Linux distribution.
All labels observed (1)
| Label | Occurrences |
|---|---|
| Gentoo ebuild writing guidelines canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T8610137 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gentoo ebuild writing guidelines Context triple: [Gentoo ebuild repository, governedBy, Gentoo ebuild writing guidelines]
-
A.
Gentoo ebuild repository
The Gentoo ebuild repository is the central collection of package build scripts and metadata that defines how software is compiled, configured, and installed in the Gentoo Linux distribution.
-
B.
Gentoo Handbook
The Gentoo Handbook is the official, comprehensive installation and configuration guide for the Gentoo Linux distribution, covering everything from initial setup to system administration.
-
C.
Gentoo Linux
Gentoo Linux is a highly customizable, source-based Linux distribution known for its performance optimization and flexibility through its Portage package management system.
-
D.
Gentoo Foundation
The Gentoo Foundation is a non-profit organization that oversees and manages the development, infrastructure, and legal affairs of the Gentoo Linux project.
-
E.
Gentoo Council
The Gentoo Council is the primary decision-making and policy-setting body that oversees the development and direction of the Gentoo Linux distribution.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Gentoo ebuild writing guidelines Target entity description: Gentoo ebuild writing guidelines are the official rules and best practices that define how software build scripts (ebuilds) must be written and maintained in the Gentoo Linux distribution.
-
A.
Gentoo ebuild repository
The Gentoo ebuild repository is the central collection of package build scripts and metadata that defines how software is compiled, configured, and installed in the Gentoo Linux distribution.
-
B.
Gentoo Handbook
The Gentoo Handbook is the official, comprehensive installation and configuration guide for the Gentoo Linux distribution, covering everything from initial setup to system administration.
-
C.
Gentoo Linux
Gentoo Linux is a highly customizable, source-based Linux distribution known for its performance optimization and flexibility through its Portage package management system.
-
D.
Gentoo Foundation
The Gentoo Foundation is a non-profit organization that oversees and manages the development, infrastructure, and legal affairs of the Gentoo Linux project.
-
E.
Gentoo Council
The Gentoo Council is the primary decision-making and policy-setting body that oversees the development and direction of the Gentoo Linux distribution.
- F. None of above. chosen
Statements (81)
| Predicate | Object |
|---|---|
| instanceOf |
Gentoo project policy
ⓘ
software development guideline ⓘ technical documentation ⓘ |
| appliesTo |
Gentoo Linux
ⓘ
Gentoo developers ⓘ
linked to:
Gentoo community
Gentoo package maintainers ⓘ ebuild ⓘ |
| appliesToFormat |
.ebuild files
ⓘ
.eclass files ⓘ |
| defines |
BDEPEND usage rules
ⓘ
HOMEPAGE field rules ⓘ IUSE field rules ⓘ QA requirements for ebuilds ⓘ RDEPEND and DEPEND usage rules ⓘ RESTRICT and PROPERTIES usage rules ⓘ SRC_URI formatting rules ⓘ USE flag handling rules ⓘ backporting and patching policies for ebuilds ⓘ best practices for maintaining ebuilds ⓘ cleanup practices in ebuilds ⓘ coding style for ebuilds ⓘ commit message conventions for ebuild changes ⓘ dependency specification rules ⓘ deprecation and removal process for ebuilds ⓘ distfile handling practices ⓘ documentation requirements for ebuilds ⓘ eclass inheritance rules ⓘ file and directory permissions in ebuilds ⓘ file header conventions for ebuilds ⓘ file naming conventions for ebuilds ⓘ handling of bundled libraries in ebuilds ⓘ handling of configuration files in ebuilds ⓘ handling of documentation and examples in ebuilds ⓘ handling of init scripts in ebuilds ⓘ handling of localization files in ebuilds ⓘ handling of network access during build ⓘ handling of static libraries in ebuilds ⓘ handling of systemd units in ebuilds ⓘ keywording practices for ebuilds ⓘ license declaration rules in ebuilds ⓘ log and temporary file handling in ebuilds ⓘ maintainer responsibilities for ebuilds ⓘ masking and unmasking practices ⓘ metadata conventions for ebuilds ⓘ mirror usage rules in ebuilds ⓘ parallel build considerations in ebuilds ⓘ patch management practices in ebuilds ⓘ phase function usage rules ⓘ pkg_* function usage rules ⓘ rules for writing ebuilds ⓘ sandbox and user privilege rules for builds ⓘ security-related practices for ebuilds ⓘ slotting and subslotting rules ⓘ stable and unstable branch policies for ebuilds ⓘ testing requirements for ebuilds ⓘ upstream collaboration practices for ebuild maintainers ⓘ use of helper eclasses in ebuilds ⓘ variable naming conventions in ebuilds ⓘ versioning conventions for ebuilds ⓘ |
| hasGoal |
ensure consistency of ebuilds
ⓘ
ensure maintainability of ebuilds ⓘ ensure policy compliance in Gentoo repository ⓘ ensure quality of Gentoo packages ⓘ ensure reproducible builds ⓘ ensure security of Gentoo packages ⓘ |
| language | English ⓘ |
| maintainedBy |
Gentoo developers
ⓘ
linked to:
Gentoo community
Gentoo project ⓘ
linked to:
Gentoo community
|
| partOf |
Gentoo development documentation
ⓘ
linked to:
Gentoo devmanual
|
| relatedTo |
Gentoo Development Guide
ⓘ
linked to:
Gentoo devmanual
Gentoo QA policies ⓘ
linked to:
Gentoo QA guidelines
Gentoo eclass guidelines ⓘ Gentoo repository policies ⓘ
linked to:
Gentoo project policies
|
| topic |
Linux distribution maintenance
ⓘ
build automation ⓘ package management ⓘ shell scripting ⓘ software packaging ⓘ |
| usedBy |
Gentoo developers
ⓘ
linked to:
Gentoo community
Gentoo package maintainers ⓘ
linked to:
Gentoo community
contributors to Gentoo ebuilds ⓘ |
How these facts were elicited
The pipeline generated the facts above by prompting gpt-5.1 with this entity's name + description and the instruction below.
Instruction
You are a knowledge base construction expert. Given a subject entity and a description of it, return factual statements that you know for the subject as a JSON list of dictionaries(triples), where keys must be "subject", "predicate" and "object". The number of facts may be very high, between 25 to 50 or more, for very popular subjects. For less popular subjects, the number of facts can be very low, like 5 or 10. # Requirements - If you don't know the subject at all, return an empty list. - If the subject is not a named entity, return an empty list. - Include at least one triple where predicate is "instanceOf". - Do not get too wordy. - Separate several objects into multiple triples with one object.
Input
Subject: Gentoo ebuild writing guidelines Description of subject: Gentoo ebuild writing guidelines are the official rules and best practices that define how software build scripts (ebuilds) must be written and maintained in the Gentoo Linux distribution.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.