Source strings

39 Strings 100%
Browse Translate
1,154 Words 100%
8,152 Characters 100%
This translation is being used as source strings within this component.

Strings status

Strings Words Characters
39 1,154 8,152
All strings Browse Translate Zen
39 1,154 8,152
Read-only strings Browse Translate Zen

Overview

Project website pagure.io/fedora-docs-l10n/packaging-guidelines
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/packaging-guidelines.git
Repository branch master
Last remote commit automatic update of pot/po files 7660837d1
♪ I'm a bot, bot, bot ♪ authored 11 hours ago
Last commit in Weblate Update translation files 59fcabe17
Weblate authored 11 hours ago
Weblate repository https://translate.fedoraproject.org/git/fedora-docs-l10n-packaging-guidelines/nav/
File mask po/*/master/pages/Ada.po
Translation file Download pot/master/pages/Ada.pot
Last change Aug. 22, 2024, 10:24 p.m.
Last change made by None
Language English
Language code en
Text direction Left to right
Number of speakers 1,728,900,209
Number of plurals 2
Plural type One/other
Plurals Singular 1
Plural 0, 2, 3, 4, 5, 6, 7, 8, 9, 10, …
Plural formula n != 1
2 days ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 39 1,154 8,152
Translated 100% 39 100% 1,154 100% 8,152
Needs editing 0% 0 0% 0 0% 0
Read-only 100% 39 100% 1,154 100% 8,152
Failing checks 0% 0 0% 0 0% 0
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 0% 0 0% 0 0% 0
Last 12 months Previous

Activity in last 12 months

0 changes 0 changes 0 changes 0 changes 1 change 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 11 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes
DecJanFebMarAprMayJunJulAugSepOctNov

Quick numbers

1,154
Hosted words
39
Hosted strings
100%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

—
Hosted words
+100%
—
Hosted strings
+100%
—
Translated
+100%
—
Contributors
—
User avatar None

Resource updated
The “pot/master/pages/Ada.pot” file was changed. 3 months ago
User avatar None

String added in the repository
Packages that use GPRinstall in the installation phase can use the macro +++<var>GPRinstall_flags</var>+++ to pass the correct pathnames and other parameters to GPRinstall.
Packages that use GPRinstall in the installation phase can use the macro +++<var>GPRinstall_flags</var>+++ to pass the correct pathnames and other parameters to GPRinstall.
3 months ago
User avatar None

String added in the repository
GPRbuild adds a runpath to the built binaries by default. Fedora’s builder flags normally include an option to disable the automatic runpath. There are however cases where it would be advantageous to allow a runpath. Libraries can have test suites or auxiliary programs that aren’t installed but run during the build and need to link to the library in the build directory, and they may rely on an automatic runpath for this. In those cases the spec file may define a macro named +++<var>GNAT_add_rpath</var>+++. The builder will then be allowed to add a runpath in those parts of the spec file where +++<var>GNAT_add_rpath</var>+++ is defined.
GPRbuild adds a runpath to the built binaries by default. Fedora’s builder flags normally include an option to disable the automatic runpath. There are however cases where it would be advantageous to allow a runpath. Libraries can have test suites or auxiliary programs that aren’t installed but run during the build and need to link to the library in the build directory, and they may rely on an automatic runpath for this. In those cases the spec file may define a macro named +++<var>GNAT_add_rpath</var>+++. The builder will then be allowed to add a runpath in those parts of the spec file where +++<var>GNAT_add_rpath</var>+++ is defined.
3 months ago
User avatar None

String added in the repository
Correct usage of the RPM macros should result in a warning message from the compiler that points out where in the code a trampoline is needed.
Correct usage of the RPM macros should result in a warning message from the compiler that points out where in the code a trampoline is needed.
3 months ago
User avatar None

String added in the repository
An executable stack has been made a linker error in Fedora. This can affect Ada packages because https://gcc.gnu.org/onlinedocs/gccint/Trampolines.html[GCC uses trampolines] to implement some language constructs. The compiler’s usage of trampolines has been greatly reduced, but https://gcc.gnu.org/onlinedocs/gnat_rm/No_005fImplicit_005fDynamic_005fCode.html[some cases remain]. One case that occurs is when a nested subprogram in Ada is passed as a callback routine to a function written in C – which means that the executable stack is also exposed to C code that may contain buffer overflows. In such cases the options are to explicitly allow an executable stack by passing “`+-largs -Wl,--no-warn-execstack+`” to GPRbuild, or restructure the code to eliminate the need for trampolines. Which option is best may depend on how exposed the program is to potentially hostile input.
An executable stack has been made a linker error in Fedora. This can affect Ada packages because https://gcc.gnu.org/onlinedocs/gccint/Trampolines.html[GCC uses trampolines] to implement some language constructs. The compiler’s usage of trampolines has been greatly reduced, but https://gcc.gnu.org/onlinedocs/gnat_rm/No_005fImplicit_005fDynamic_005fCode.html[some cases remain]. One case that occurs is when a nested subprogram in Ada is passed as a callback routine to a function written in C – which means that the executable stack is also exposed to C code that may contain buffer overflows. In such cases the options are to explicitly allow an executable stack by passing “`+-largs -Wl,--no-warn-execstack+`” to GPRbuild, or restructure the code to eliminate the need for trampolines. Which option is best may depend on how exposed the program is to potentially hostile input.
3 months ago
User avatar None

String added in the repository
Trampolines
Trampolines
3 months ago
User avatar None

String added in the repository
If the upstream source package comes with a build system, for example a GNAT project file or makefiles and a configuration script, then it’s probably best to use that if possible. If not, it is recommended that the packager write a GNAT project file and use GPRbuild to control the compilation.
If the upstream source package comes with a build system, for example a GNAT project file or makefiles and a configuration script, then it’s probably best to use that if possible. If not, it is recommended that the packager write a GNAT project file and use GPRbuild to control the compilation.
3 months ago
User avatar None

String added in the repository
The macros +++<var>GPRbuild_arches</var>+++ and +++<var>GNAT_arches</var>+++ expand to a list of architectures where GNAT packages are available in Fedora. When there is a need to prevent attempts to build an Ada package on secondary architectures where GNAT has not been bootstrapped, this *MUST* be done with either “`+ExclusiveArch: %{GPRbuild_arches}+`” or “`+ExclusiveArch: %{GNAT_arches}+`”.
The macros +++<var>GPRbuild_arches</var>+++ and +++<var>GNAT_arches</var>+++ expand to a list of architectures where GNAT packages are available in Fedora. When there is a need to prevent attempts to build an Ada package on secondary architectures where GNAT has not been bootstrapped, this *MUST* be done with either “`+ExclusiveArch: %{GPRbuild_arches}+`” or “`+ExclusiveArch: %{GNAT_arches}+`”.
3 months ago
User avatar None

String added in the repository
In case a package’s build system invokes the underlying GNAT tools without using GPRbuild or Gnatmake, then the appropriate macro for each tool *MUST* be used. If for example Gnatlink is invoked directly, then the expansion of +++<var>Gnatlink_flags</var>+++ shall be passed to it.
In case a package’s build system invokes the underlying GNAT tools without using GPRbuild or Gnatmake, then the appropriate macro for each tool *MUST* be used. If for example Gnatlink is invoked directly, then the expansion of +++<var>Gnatlink_flags</var>+++ shall be passed to it.
3 months ago
User avatar None

String added in the repository
For packages that are built with GPRbuild or Gnatmake but without Comfignat there are the macros +++<var>GPRbuild_flags</var>+++ and +++<var>Gnatmake_flags</var>+++, which contain builder, compiler and linker flags.
For packages that are built with GPRbuild or Gnatmake but without Comfignat there are the macros +++<var>GPRbuild_flags</var>+++ and +++<var>Gnatmake_flags</var>+++, which contain builder, compiler and linker flags.
3 months ago
Browse all translation changes