Overview

Project website pagure.io/fedora-docs-l10n/modularity
Instructions for translators

Mailing list for translators: <<trans@lists.fedoraproject.org>
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Any authenticated user can contribute.
  • The translation uses bilingual files.
Translation license Creative Commons Attribution Share Alike 3.0 Unported
Source code repository ssh://pagure.io/fedora-docs-l10n/modularity.git
Repository branch master
Last remote commit Update translation files a812594c
Weblate authored a month ago
Weblate repository https://translate.fedoraproject.org/git/fedora-docs-l10n-modularity/nav/
File mask po/*/master/pages/core-concepts/module-buildorder.po
Translation file Download po/fr/master/pages/core-concepts/module-buildorder.po
Last change None
Last author None

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 7 562 4,128
Translated 0% 0 0% 0 0% 0
Needs editing 0% 0 0% 0 0% 0
Read-only 0% 0 0% 0 0% 0
Failing checks 0% 0 0% 0 0% 0
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 100% 7 100% 562 100% 4,128
Last 12 months Previous

Activity in last 12 months

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

Quick numbers

562
Hosted words
7
Hosted strings
0%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

—
Hosted words
—
—
Hosted strings
—
—
Translated
—
—
Contributors
—
User avatar None

Resource update

fedora-docs-l10n/modularity / master/pages/core-concepts/module-buildorder — French

The "po/fr/master/pages/core-concepts/module-buildorder.po" file was changed. a year ago
User avatar None

New strings to translate

fedora-docs-l10n/modularity / master/pages/core-concepts/module-buildorder — French

7 new strings to translate appeared to the translation. a year ago
User avatar None

Resource update

fedora-docs-l10n/modularity / master/pages/core-concepts/module-buildorder — French

File po/fr/master/pages/core-concepts/module-buildorder.po was added. a year ago
User avatar None

String updated in the repository

fedora-docs-l10n/modularity / master/pages/core-concepts/module-buildorder — French

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.
 
a year ago
User avatar None

String updated in the repository

fedora-docs-l10n/modularity / master/pages/core-concepts/module-buildorder — French

⋮
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
⋮
 
a year ago
User avatar None

String updated in the repository

fedora-docs-l10n/modularity / master/pages/core-concepts/module-buildorder — French

build order of a `perl-bootstrap:5.32` module stream
 
a year ago
User avatar None

String updated in the repository

fedora-docs-l10n/modularity / master/pages/core-concepts/module-buildorder — French

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.
+
+
 
a year ago
User avatar None

String updated in the repository

fedora-docs-l10n/modularity / master/pages/core-concepts/module-buildorder — French

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.
 
a year ago
User avatar None

String updated in the repository

fedora-docs-l10n/modularity / master/pages/core-concepts/module-buildorder — French

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.
 
a year ago
User avatar None

String updated in the repository

fedora-docs-l10n/modularity / master/pages/core-concepts/module-buildorder — French

Module build order
 
a year ago
Browse all translation changes