fedora-docs-l10n/modularity

master/pages/core-concepts/module-buildorder

	Language	Translated	Unfinished	Unfinished words	Unfinished characters	Untranslated	Checks	Suggestions	Comments
	English CC-BY-SA-3.0		0	0	0	0	0	0	0

	French CC-BY-SA-3.0	0%	7	562	4,128	7	0	0	0

	Spanish CC-BY-SA-3.0	0%	7	562	4,128	7	0	0	0

Please sign in to see the alerts.

Overview

Project website	pagure.io/fedora-docs-l10n/modularity
Instructions for translators	Mailing list for translators: <<trans@lists.fedoraproject.org>
Translation license	Creative Commons Attribution Share Alike 3.0 Unported
Translation process	Translations can be made directly. Translation suggestions can be made. Any authenticated user can contribute. The translation uses bilingual files.
Source code repository	`ssh://pagure.io/fedora-docs-l10n/modularity.git`
Repository branch	master
Last remote commit	automatic update of pot/po files `d453d4ba` ♪ I'm a bot, bot, bot ♪ authored 5 months ago
Weblate repository	`https://translate.fedoraproject.org/git/fedora-docs-l10n-modularity/nav/`
File mask	`po/*/master/pages/core-concepts/module-buildorder.po`

12 days ago

String statistics

	Strings percent	Hosted strings	Words percent	Hosted words	Characters percent	Hosted characters
Total		21		1,686		12,384
Source		7		562		4,128
Translated	33%	7	33%	562	33%	4,128
Needs editing	0%	0	0%	0	0%	0
Read-only	33%	7	33%	562	33%	4,128
Failing checks	0%	0	0%	0	0%	0
Strings with suggestions	0%	0	0%	0	0%	0
Untranslated strings	66%	14	66%	1,124	66%	8,256

Last 12 months Previous

Activity in last 12 months


Apr	May	Jun	Jul	Aug	Sep	Oct	Nov	Dec	Jan	Feb	Mar

Quick numbers

1,686

Hosted words

21

Hosted strings

33%

Translated

and previous 30 days

Trends of last 30 days

—

Hosted words

+100%

—

Hosted strings

+100%

—

Translated

+33%

—

Contributors

+100%

Search

Advanced query builder

Query examples

Review strings changed by other users	`changed:>=2024-03-25 AND NOT changed_by:anonymous`	Add
Translated strings	`state:>=translated`	Add
Strings with comments	`has:comment`	Add
Strings with any failing checks	`has:check`	Add
Strings with suggestions from others	`has:suggestion AND NOT suggestion_author:anonymous`	Add
Approved strings with suggestions	`state:approved AND has:suggestion`	Add
All untranslated strings added the past month	`added:>=2024-03-25 AND state:<=needs-editing`	Add
Translated strings in a certain language	`is:translated AND language:en`	Add

None Resource updated fedora-docs-l10n/modularity master/pages/core-concepts/module-buildorder Spanish	File `po/es/master/pages/core-concepts/module-buildorder.po` was added. 3 months ago
None String updated in the repository fedora-docs-l10n/modularity master/pages/core-concepts/module-buildorder Spanish	English In this example we have the build order of the `perl-bootstrap:5.32` module. The component with the lowest `buildorder` number will start building first. In our case this is the package `perl` with the `buildorder` number 0. All the other component (package) builds need to wait until the first build batch is built. A build batch consists of packages which share the same `buildorder` number. After the `perl` package is built then the build batch has finished building all its components and can move to a higher order of the build order. The build of package `perl` needs to be added and enabled to the buildroot of the build of packages of the next `buildorder` number. In our case the next build batch is the build batch with the `buildorder` number 2. A build batch can have one or more packages. This means that the packages can be built simultaneously. Each build batch uses all the previous build batches as build dependencies which are available and enabled in its buildroots. The only build batch which does not have any previous build batch dependencies is the build batch with `buildorder` number 0. The only build batch which is not used as build batch dependencies is the build batch with the highest `buildorder` number. In our example the build batch with `buildorder` number 5 consists of 9 packages and number 4 consists of over 100 packages. All the packages built in build batches of `buildorder` numbers 0-4 will be used as build time dependencies for the build batch with the `buildorder` number 5. Spanish 0 characters edited Current translation Empty 3 months ago
None String updated in the repository fedora-docs-l10n/modularity master/pages/core-concepts/module-buildorder Spanish	English ⋮ components: rpms: perl: rationale: The Perl interpreter. ref: f33 buildorder: 0 perl-Fedora-VSP: rationale: A build dependency. ref: f33 buildorder: 1 perl-generators: rationale: A build dependency. ref: f33 buildorder: 2 perl-Algorithm-Diff: rationale: A build dependency. ref: f33 buildorder: 3 ⋮ perl-Config-AutoConf: rationale: A build dependency. ref: f33 buildorder: 4 ⋮ perl-IO-Compress-Lzma: rationale: A build dependency. ref: f33 buildorder: 5 ⋮ perl-Data-OptList: rationale: A build dependency. ref: f33 buildorder: 6 ⋮ perl-Sub-Exporter: rationale: A build dependency. ref: f33 buildorder: 7 perl-Data-Section: rationale: A build dependency. ref: f33 buildorder: 8 perl-Software-License: rationale: A build dependency. ref: f33 buildorder: 9 ⋮ Spanish 0 characters edited Current translation Empty 3 months ago
None String updated in the repository fedora-docs-l10n/modularity master/pages/core-concepts/module-buildorder Spanish	English build order of a `perl-bootstrap:5.32` module stream Spanish 0 characters edited Current translation Empty 3 months ago
None String updated in the repository fedora-docs-l10n/modularity master/pages/core-concepts/module-buildorder Spanish	English If the `buildorder` property is specified for each component of the module stream, the build system needs to respect this ordering. This means that each `buildorder` number represents a group or a batch of packages that need to be built together. Each higher “build batch” needs the RPM artifacts from the previous build batches to be present and enabled in the current one. So they can serve as dependencies for the current batch. This continues until the last batch is built. The last batch will contain all the other artifacts from the previous batches. + + Spanish 0 characters edited Current translation Empty 3 months ago
None String updated in the repository fedora-docs-l10n/modularity master/pages/core-concepts/module-buildorder Spanish	English By default, if no `buildorder` property is specified the build order of the packages is equal to 0 for the purposes of the module stream build. This means that all the packages can be built at the same time. Spanish 0 characters edited Current translation Empty 3 months ago
None String updated in the repository fedora-docs-l10n/modularity master/pages/core-concepts/module-buildorder Spanish	English Packages which are built within a module stream can have dependency relationships between them. This means that packages within a module can use other packages from the same module as build or runtime dependencies. For this to be possible we are using the `buildorder` property which can be added to each of the components defined in a module stream. Spanish 0 characters edited Current translation Empty 3 months ago
None String updated in the repository fedora-docs-l10n/modularity master/pages/core-concepts/module-buildorder Spanish	English Module build order Spanish 0 characters edited Current translation Empty 3 months ago
None Changes committed fedora-docs-l10n/modularity master/pages/core-concepts/module-buildorder Spanish	Changes committed 3 months ago
None Alert triggered fedora-docs-l10n/modularity master/pages/core-concepts/module-buildorder	Component seems unused. 11 months ago

Browse all component changes