Portage metadata format
E745839
Portage metadata format is a structured specification used by Gentoo’s package management system to describe package properties, dependencies, and related metadata within ebuild repositories.
All labels observed (1)
| Label | Occurrences |
|---|---|
| Portage metadata format canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T8610109 — 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: Portage metadata format Context triple: [Gentoo ebuild repository, uses, Portage metadata format]
-
A.
Manifest V2
Manifest V2 is an older version of the Chrome and WebExtensions extension manifest format that defines how browser extensions are structured, behave, and request permissions.
-
B.
Atom package registry
Atom package registry is the online repository where developers publish and share extensions and packages that enhance the functionality of the Atom text editor.
-
C.
S-100 metadata framework
The S-100 metadata framework is an IHO-developed standard that defines a flexible, interoperable structure for describing and managing geospatial and hydrographic data within the broader S-100 universal hydrographic data model.
-
D.
Open Packaging Conventions
Open Packaging Conventions is a standardized container and packaging format, best known for underpinning modern Office document file types like .docx, .xlsx, and .pptx by organizing content as structured ZIP-based packages.
-
E.
PEP 621 (project metadata in pyproject.toml, partially)
PEP 621 is a Python packaging standard that defines a standardized way to declare project metadata in the `pyproject.toml` file.
- 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: Portage metadata format Target entity description: Portage metadata format is a structured specification used by Gentoo’s package management system to describe package properties, dependencies, and related metadata within ebuild repositories.
-
A.
Manifest V2
Manifest V2 is an older version of the Chrome and WebExtensions extension manifest format that defines how browser extensions are structured, behave, and request permissions.
-
B.
Atom package registry
Atom package registry is the online repository where developers publish and share extensions and packages that enhance the functionality of the Atom text editor.
-
C.
S-100 metadata framework
The S-100 metadata framework is an IHO-developed standard that defines a flexible, interoperable structure for describing and managing geospatial and hydrographic data within the broader S-100 universal hydrographic data model.
-
D.
Open Packaging Conventions
Open Packaging Conventions is a standardized container and packaging format, best known for underpinning modern Office document file types like .docx, .xlsx, and .pptx by organizing content as structured ZIP-based packages.
-
E.
PEP 621 (project metadata in pyproject.toml, partially)
PEP 621 is a Python packaging standard that defines a standardized way to declare project metadata in the `pyproject.toml` file.
- F. None of above. chosen
Statements (67)
| Predicate | Object |
|---|---|
| instanceOf |
Gentoo-specific specification
ⓘ
software metadata format ⓘ |
| associatedWith |
Gentoo Linux
NERFINISHED
ⓘ
Gentoo ebuild format NERFINISHED ⓘ |
| defines |
package dependencies
ⓘ
package metadata ⓘ package properties ⓘ repository-level metadata ⓘ |
| documentedIn |
Gentoo PMS (Package Manager Specification)
NERFINISHED
ⓘ
Gentoo Wiki NERFINISHED ⓘ Gentoo devmanual NERFINISHED ⓘ |
| governedBy | EAPI specifications ⓘ |
| includesConcept |
BDEPEND metadata
ⓘ
DEPEND metadata ⓘ DESCRIPTION metadata ⓘ HOMEPAGE metadata ⓘ IUSE metadata ⓘ KEYWORDS metadata ⓘ LICENSE metadata ⓘ Manifest file format ⓘ PDEPEND metadata ⓘ PROPERTIES metadata ⓘ RDEPEND metadata ⓘ REQUIRED_USE metadata ⓘ RESTRICT metadata ⓘ SLOT metadata ⓘ SRC_URI metadata ⓘ eapi specification ⓘ license groups ⓘ metadata.xml ⓘ profiles/arch.list ⓘ profiles/base ⓘ profiles/desc files ⓘ profiles/package.accept_keywords ⓘ profiles/package.accept_restrict ⓘ profiles/package.mask ⓘ profiles/package.provided ⓘ profiles/package.use ⓘ profiles/package.use.force ⓘ profiles/package.use.mask ⓘ profiles/parent ⓘ profiles/updates ⓘ profiles/use.force ⓘ profiles/use.mask ⓘ profiles/virtuals ⓘ repository categories ⓘ repository metadata layout.conf ⓘ slot and subslot semantics ⓘ use flag descriptions ⓘ |
| supports |
ebuilds
ⓘ
eclasses ⓘ profiles ⓘ repository configuration ⓘ |
| supportsFeature |
fine-grained masking
ⓘ
incremental configuration files ⓘ per-architecture keywords ⓘ per-profile configuration ⓘ signed Manifests ⓘ |
| usedBy |
Gentoo package management system
NERFINISHED
ⓘ
Portage NERFINISHED ⓘ |
| usedFor |
USE flag handling
ⓘ
dependency resolution ⓘ keywording and stabilization ⓘ license compliance checking ⓘ package visibility control ⓘ repository synchronization ⓘ |
| usedIn | Gentoo ebuild repositories ⓘ |
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: Portage metadata format Description of subject: Portage metadata format is a structured specification used by Gentoo’s package management system to describe package properties, dependencies, and related metadata within ebuild repositories.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.