guix/documentation-manual — Chinese (Simplified) (zh_CN) @ Fedora Weblate: #!location/of/bin/bash export PATH="/gnu/.../bar/bin" export CERT_PATH="$CERT_PATH$@{CERT_PATH:+:@}/gnu/.../baz/certs:/qux/certs" exec -a $0 location/of/.foo-real "$@@"

Zen

Translation

English type: example

Chinese (Simplified) (zh_CN)

Needs editing

Skip

	English	Chinese (Simplified) (zh_CN)	Actions
	program wrappers	程序包装器
	wrapping programs	包装程序
	It is not unusual for a command to require certain environment variables to be set for proper functioning, typically search paths (@pxref{Search Paths}). Failing to do that, the command might fail to find files or other commands it relies on, or it might pick the ``wrong'' ones---depending on the environment in which it runs. Examples include:	命令需要设置某些环境变量以正常运行并不罕见，通常是搜索路径 (@pxref{Search Paths})。如果不这样做，命令可能无法找到它依赖的文件或其他命令，或者可能选择“错误”的命令——这取决于它运行的环境。示例包括：
	a shell script that assumes all the commands it uses are in @env{PATH};	一个假设它使用的所有命令都在 @env{PATH} 中的 shell 脚本；
	a Guile program that assumes all its modules are in @env{GUILE_LOAD_PATH} and @env{GUILE_LOAD_COMPILED_PATH};	一个假设它的所有模块都在 @env{GUILE_LOAD_PATH} 和 @env{GUILE_LOAD_COMPILED_PATH} 中的 Guile 程序；
	a Qt application that expects to find certain plugins in @env{QT_PLUGIN_PATH}.	一个期望在 @env{QT_PLUGIN_PATH} 中找到某些插件的 Qt 应用程序。
	For a package writer, the goal is to make sure commands always work the same rather than depend on some external settings. One way to achieve that is to @dfn{wrap} commands in a thin script that sets those environment variables, thereby ensuring that those run-time dependencies are always found. The wrapper would be used to set @env{PATH}, @env{GUILE_LOAD_PATH}, or @env{QT_PLUGIN_PATH} in the examples above.	对于软件包编写者来说，目标是确保命令始终以相同的方式工作，而不是依赖某些外部设置。实现这一目标的一种方法是 @dfn{包装} 命令在一个薄脚本中，该脚本设置这些环境变量，从而确保这些运行时依赖项始终被找到。包装器将用于在上述示例中设置 @env{PATH}、@env{GUILE_LOAD_PATH} 或 @env{QT_PLUGIN_PATH}。
	To ease that task, the @code{(guix build utils)} module provides a couple of helpers to wrap commands.	为了简化该任务，@code{(guix build utils)} 模块提供了一些帮助程序来包装命令。
	{Procedure} wrap-program program [#:sh sh] [#:rest variables]	{Procedure} wrap-program program [#:sh sh] [#:rest variables]
	Make a wrapper for @var{program}. @var{variables} should look like this:	为 @var{program} 创建一个包装器。 @var{variables} 应该看起来像这样：
	'(@var{variable} @var{delimiter} @var{position} @var{list-of-directories})	'(@var{variable} @var{delimiter} @var{position} @var{list-of-directories})
	where @var{delimiter} is optional. @code{:} will be used if @var{delimiter} is not given.	其中 @var{delimiter} 是可选的。如果没有给出 @var{delimiter}，将使用 @code{:}。
	For example, this call:	例如，这个调用：
	(wrap-program "foo" '("PATH" ":" = ("/gnu/.../bar/bin")) '("CERT_PATH" suffix ("/gnu/.../baz/certs" "/qux/certs")))	(wrap-program "foo" '("PATH" ":" = ("/gnu/.../bar/bin")) '("CERT_PATH" suffix ("/gnu/.../baz/certs" "/qux/certs")))
	will copy @file{foo} to @file{.foo-real} and create the file @file{foo} with the following contents:	将 @file{foo} 复制到 @file{.foo-real} 并创建文件 @file{foo}，其内容如下：
	#!location/of/bin/bash export PATH="/gnu/.../bar/bin" export CERT_PATH="$CERT_PATH$@{CERT_PATH:+:@}/gnu/.../baz/certs:/qux/certs" exec -a $0 location/of/.foo-real "$@@"	#!location/of/bin/bash\nexport PATH="/gnu/.../bar/bin"\nexport CERT_PATH="$CERT_PATH$@{CERT_PATH:+:@}/gnu/.../baz/certs:/qux/certs"\nexec -a $0 location/of/.foo-real "$@@"\n
	If @var{program} has previously been wrapped by @code{wrap-program}, the wrapper is extended with definitions for @var{variables}. If it is not, @var{sh} will be used as the interpreter.	如果 @var{program} 之前已被 @code{wrap-program} 包装，则包装器将扩展 @var{variables} 的定义。如果没有，将使用 @var{sh} 作为解释器。
	{Procedure} wrap-script program [#:guile guile] [#:rest variables]	{Procedure} wrap-script 程序 [#:guile guile] [#:rest 变量]
	Wrap the script @var{program} such that @var{variables} are set first. The format of @var{variables} is the same as in the @code{wrap-program} procedure. This procedure differs from @code{wrap-program} in that it does not create a separate shell script. Instead, @var{program} is modified directly by prepending a Guile script, which is interpreted as a comment in the script's language.	将脚本 @var{program} 包装，使得 @var{variables} 首先被设置。 @var{variables} 的格式与 @code{wrap-program} 过程中的格式相同。此过程与 @code{wrap-program} 的不同之处在于它不创建单独的 shell 脚本。相反，@var{program} 通过在其前面添加一个 Guile 脚本直接进行修改，该脚本在脚本语言中被解释为注释。
	Special encoding comments as supported by Python are recreated on the second line.	Python 支持的特殊编码注释在第二行重新创建。
	Note that this procedure can only be used once per file as Guile scripts are not supported.	请注意，此过程每个文件只能使用一次，因为不支持 Guile 脚本。
	search path	搜索路径
	Many programs and libraries look for input data in a @dfn{search path}, a list of directories: shells like Bash look for executables in the command search path, a C compiler looks for @file{.h} files in its header search path, the Python interpreter looks for @file{.py} files in its search path, the spell checker has a search path for dictionaries, and so on.	许多程序和库在 @dfn{搜索路径} 中查找输入数据，这是一个目录列表：像 Bash 这样的 shell 在命令搜索路径中查找可执行文件，C 编译器在其头文件搜索路径中查找 @file{.h} 文件，Python 解释器在其搜索路径中查找 @file{.py} 文件，拼写检查器有一个字典的搜索路径，等等。
	Search paths can usually be defined or overridden @i{via} environment variables (@pxref{Environment Variables,,, libc, The GNU C Library Reference Manual}). For example, the search paths mentioned above can be changed by defining the @env{PATH}, @env{C_INCLUDE_PATH}, @env{PYTHONPATH} (or @env{GUIX_PYTHONPATH}), and @env{DICPATH} environment variables---you know, all these something-PATH variables that you need to get right or things ``won't be found''.	搜索路径通常可以通过环境变量 @i{via} 定义或覆盖 (@pxref{Environment Variables,,, libc, The GNU C Library Reference Manual})。例如，上述搜索路径可以通过定义 @env{PATH}、@env{C_INCLUDE_PATH}、@env{PYTHONPATH}（或 @env{GUIX_PYTHONPATH}）和 @env{DICPATH} 环境变量来更改——你知道的，所有这些需要正确设置的某种 PATH 变量，否则东西“找不到”。
	You may have noticed from the command line that Guix ``knows'' which search path environment variables should be defined, and how. When you install packages in your default profile, the file @file{~/.guix-profile/etc/profile} is created, which you can ``source'' from the shell to set those variables. Likewise, if you ask @command{guix shell} to create an environment containing Python and NumPy, a Python library, and if you pass it the @option{--search-paths} option, it will tell you about @env{PATH} and @env{GUIX_PYTHONPATH} (@pxref{Invoking guix shell}):	你可能已经注意到，从命令行中，Guix “知道” 应该定义哪些搜索路径环境变量，以及如何定义。当你在默认配置文件中安装软件包时，会创建文件 @file{~/.guix-profile/etc/profile}，你可以从 shell 中“source”该文件以设置这些变量。同样，如果你请求 @command{guix shell} 创建一个包含 Python 和 NumPy（一个 Python 库）的环境，并且如果你传递 @option{--search-paths} 选项，它会告诉你关于 @env{PATH} 和 @env{GUIX_PYTHONPATH} 的信息 (@pxref{Invoking guix shell}):
	$ guix shell python python-numpy --pure --search-paths export PATH="/gnu/store/@dots{}-profile/bin" export GUIX_PYTHONPATH="/gnu/store/@dots{}-profile/lib/python3.9/site-packages"	$ guix shell python python-numpy --pure --search-paths export PATH="/gnu/store/@dots{}-profile/bin" export GUIX_PYTHONPATH="/gnu/store/@dots{}-profile/lib/python3.9/site-packages"
	When you omit @option{--search-paths}, it defines these environment variables right away, such that Python can readily find NumPy:	当您省略 @option{--search-paths} 时，它会立即定义这些环境变量，以便 Python 可以轻松找到 NumPy：
	$ guix shell python python-numpy -- python3 Python 3.9.6 (default, Jan 1 1970, 00:00:01) [GCC 10.3.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> import numpy >>> numpy.version.version '1.20.3'	$ guix shell python python-numpy -- python3 Python 3.9.6 (默认，1970年1月1日，00:00:01) [GCC 10.3.0] 在 linux 上输入 "help", "copyright", "credits" 或 "license" 获取更多信息。 >>> import numpy >>> numpy.version.version '1.20.3'
	For this to work, the definition of the @code{python} package @emph{declares} the search path it cares about and its associated environment variable, @env{GUIX_PYTHONPATH}. It looks like this:	为了使其工作，@code{python} 包的定义 @emph{声明} 了它关心的搜索路径及其相关的环境变量 @env{GUIX_PYTHONPATH}。它看起来像这样：
	(package (name "python") (version "3.9.9") ;; some fields omitted... (native-search-paths (list (search-path-specification (variable "GUIX_PYTHONPATH") (files (list "lib/python/3.9/site-packages"))))))	(package (name "python") (version "3.9.9") ;; 一些字段省略... (native-search-paths (list (search-path-specification (variable "GUIX_PYTHONPATH") (files (list "lib/python/3.9/site-packages"))))))
	What this @code{native-search-paths} field says is that, when the @code{python} package is used, the @env{GUIX_PYTHONPATH} environment variable must be defined to include all the @file{lib/python/3.9/site-packages} sub-directories encountered in its environment. (The @code{native-} bit means that, if we are in a cross-compilation environment, only native inputs may be added to the search path; @pxref{package Reference, @code{search-paths}}.) In the NumPy example above, the profile where @code{python} appears contains exactly one such sub-directory, and @env{GUIX_PYTHONPATH} is set to that. When there are several @file{lib/python/3.9/site-packages}---this is the case in package build environments---they are all added to @env{GUIX_PYTHONPATH}, separated by colons (@code{:}).	这个 @code{native-search-paths} 字段的意思是，当使用 @code{python} 包时，必须定义 @env{GUIX_PYTHONPATH} 环境变量，以包含其环境中遇到的所有 @file{lib/python/3.9/site-packages} 子目录。(@code{native-} 的意思是，如果我们处于交叉编译环境中，则只能将本地输入添加到搜索路径中；@pxref{package Reference, @code{search-paths}}。) 在上面的 NumPy 示例中，@code{python} 出现的配置文件恰好包含一个这样的子目录，而 @env{GUIX_PYTHONPATH} 被设置为该目录。当有多个 @file{lib/python/3.9/site-packages} 时——这在包构建环境中是常见的——它们都被添加到 @env{GUIX_PYTHONPATH} 中，以冒号 (@code{:}) 分隔。

mt:weblate-translation-memory

Suggestion added

Suggested change:

Failing checks:

Mismatched \n Mismatching line breaks 10 days ago

Loading…

mt:weblate-translation-memory

Suggestion added

English

Chinese (Simplified) (zh_CN) 0 characters edited Current translation

10 days ago

pelzflorian

Translation uploaded

English

Chinese (Simplified) (zh_CN) 0 characters edited Current translation Needs editing

11 days ago

clsty

Translation uploaded

English

Chinese (Simplified) (zh_CN) 174 characters edited Current translation Translated

2 weeks ago

Browse all string changes

Things to check

Suggestions

There is 1 suggestion for this string.

View

Mismatched \n

Number of \n literals in translation does not match source

Reset

Mismatching line breaks

Number of new lines in translation does not match source

Reset

Glossary

English	Chinese (Simplified) (zh_CN)
No related strings found in the glossary.

9832579 String information

Source string description

type: example

Flags

no-wrap

Source string location

guix-git/doc/guix.texi:11114

String age

2 years ago

Last updated

2 days ago

Source string age

2 years ago

Translation file

po/doc/guix-manual.zh_CN.po, string 4088

Shortcut	Action
`?`	Open available keyboard shortcuts.
`Alt` + `Home`	Navigate to the first translation in the current search.
`Alt` + `End`	Navigate to the last translation in the current search.
`Alt` + `PageUp` or `Ctrl` + `↑` or `Alt` + `↑` or `Cmd` + `↑` or	Navigate to the last translation in the current search.
`Alt` + `PageDown` or `Ctrl` + `↓` or `Alt` + `↓` or `Cmd` + `↓` or	Navigate to the next translation in the current search.
`Ctrl` + `Enter` or `Cmd` + `Enter`	Submit current form; this works the same as pressing Save and continue while editing translation.
`Ctrl` + `Shift` + `Enter` or `Cmd` + `Shift` +`Enter`	Unmark translation as Needing edit and submit it.
`Alt` + `Enter` or `Option` + `Enter`	Submit the string as a suggestion; this works the same as pressing Suggest while editing translation.
`Ctrl` + `E` or `Cmd` + `E`	Focus on translation editor.
`Ctrl` + `U` or `Cmd` + `U`	Focus on comment editor.
`Ctrl` + `M` or `Cmd` + `M`	Shows Automatic suggestions tab.
`Ctrl` + `1` to `Ctrl` + `9` or `Cmd` + `1` to `Cmd` + `9`	Copies placeable of a given number from source string.
`Ctrl` + `M` followed by `1` to `9` or `Cmd` + `M` followed by `1` to `9`	Copy the machine translation of a given number to current translation.
`Ctrl` + `I` followed by `1` to `9` or `Cmd` + `I` followed by `1` to `9`	Ignore one item in the list of failing checks.
`Ctrl` + `J` or `Cmd` + `J`	Shows the Nearby strings tab.
`Ctrl` + `S` or `Cmd` + `S`	Focus on search field.
`Ctrl` + `O` or `Cmd` + `O`	Copy the source string.
`Ctrl` + `Y` or `Cmd` + `Y`	Toggle the Needs editing checkbox.
`→`	Browse the next translation string.
`←`	Browse the previous translation string.