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 13 hours ago
Last commit in Weblate Translated using Weblate (Finnish) f7d1b7bc6
User avatar tigg authored 56 minutes ago
Weblate repository https://translate.fedoraproject.org/git/fedora-docs-l10n-packaging-guidelines/nav/
File mask po/*/master/pages/Ada.po
Translation file Download po/pt_BR/master/pages/Ada.po
Last change Aug. 22, 2024, 10:24 p.m.
Last change made by None
Language Portuguese (Brazil)
Language code pt_BR
Text direction Left to right
Number of speakers 200,247,320
Number of plurals 2
Plural type One/other
Plurals Singular 0, 1
Plural 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, …
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 0% 0 0% 0 0% 0
Needs editing 74% 29 64% 742 64% 5,233
Read-only 0% 0 0% 0 0% 0
Failing checks 2% 1 4% 51 4% 398
Strings with suggestions 2% 1 1% 3 1% 24
Untranslated strings 25% 10 35% 412 35% 2,919
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
0%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

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

Resource updated
The “po/pt_BR/master/pages/Ada.po” 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.
 
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.
Gnatmake e GPRbuild adicionam um runpath aos binários construídos por padrão. As flags do builder do Fedora normalmente incluem uma opção para desabilitar o runpath automático. No entanto, há casos em que seria vantajoso permitir um caminho de execução. As bibliotecas podem ter suítes de teste ou programas auxiliares que não são instalados, mas são executados durante a compilação e precisam ser vinculados à biblioteca no diretório de compilação, e podem contar com um caminho de execução automático para isso. Nesses casos, o arquivo de especificação pode definir uma macro chamada +++<var>GNAT_add_rpath</var>+++. Os construtores terão então permissão para adicionar um caminho de execução nas partes do arquivo de especificação onde +++<var>GNAT_add_rpath</var>+++ é definido.
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.
 
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.
 
3 months ago
User avatar None

String added in the repository
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.
Se o pacote de origem upstream vier com um sistema de construção, por exemplo, um arquivo de projeto GNAT ou makefiles e um script de configuração, então provavelmente é melhor usar isso, se possível. Caso contrário, é recomendado que o empacotador escreva um arquivo de projeto GNAT para controlar a compilação.
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}+`”.
A macro +++<var>GNAT_arches</var>+++ se expande para uma lista de arquiteturas onde os pacotes GNAT estão disponíveis no Fedora. A partir do Fedora 18, quando houver necessidade de evitar tentativas de construir um pacote Ada em arquiteturas secundárias onde GNAT não foi inicializado, isso *DEVE* ser feito com “`+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.
No caso de o sistema de compilação de um pacote invocar as ferramentas GNAT subjacentes sem usar Gnatmake ou GPRbuild, a macro apropriada para cada ferramenta *DEVE* ser usada. Se, por exemplo, Gnatlink for invocado diretamente, então a expansão de +++<var>Gnatlink_flags</var>+++ deve ser passada para ele.
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.
Para pacotes que são construídos com Gnatmake ou GPRbuild, mas sem Comfignat, existem as macros +++<var>Gnatmake_optflags</var>+++ e +++<var>GPRbuild_optflags</var>+++, que contêm builder, flags de compilador e linker.
3 months ago
Browse all translation changes