Zen

Translation

English type: quotation
Warning
8/100 · 7

Sign in to save the translation.

English Russian Actions
The next step is to create files containing package modules (@pxref{Package Modules}), each of which will contain one or more package definitions (@pxref{Defining Packages}). A channel can provide things other than packages, such as build systems or services; we're using packages as it's the most common use case.
 
For example, Alice might want to provide a module called @code{(alice packages greetings)} that will provide her favorite ``hello world'' implementations. To do that Alice will create a directory corresponding to that module name.
 
mkdir -p alice/packages
$EDITOR alice/packages/greetings.scm
git add alice/packages/greetings.scm
 
You can name your package modules however you like; the main constraint to keep in mind is to avoid name clashes with other package collections, which is why our hypothetical Alice wisely chose the @code{(alice packages @dots{})} name space.
 
Note that you can also place modules in a sub-directory of the repository; @pxref{Package Modules in a Sub-directory}, for more info on that.
 
With this first module in place, the next step is to test the packages it provides. This can be done with @command{guix build}, which needs to be told to look for modules in the Git checkout. For example, assuming @code{(alice packages greetings)} provides a package called @code{hi-from-alice}, Alice will run this command from the Git checkout:
 
guix build -L. hi-from-alice
guix build --rounds=2 my-package
... where @code{-L.} adds the current directory to Guile's load path (@pxref{Load Paths,,, guile, GNU Guile Reference Manual}).
 
It might take Alice a few iterations to obtain satisfying package definitions. Eventually Alice will commit this file:
 
git commit
commit
As a channel author, consider bundling authentication material with your channel so that users can authenticate it. @xref{Channel Authentication}, and @ref{Specifying Channel Authorizations}, for info on how to do it.
Как автор канала, рассмотрите возможность объединения материалов для аутентификации с вашим каналом, чтобы пользователи могли его аутентифицировать. @xref{Channel Authentication} и @ref{Specifying Channel Authorizations} для получения информации о том, как это сделать.
To use Alice's channel, anyone can now add it to their channel file (@pxref{Specifying Additional Channels}) and run @command{guix pull} (@pxref{Invoking guix pull}):
 
$EDITOR ~/.config/guix/channels.scm
guix pull
пользовательский файл @file{~/.config/guix/channels.scm};
Guix will now behave as if the root directory of that channel's Git repository had been permanently added to the Guile load path. In this example, @code{(alice packages greetings)} will automatically be found by the @command{guix} command.
 
Voilà!
 
Warning
Внимание
Before you publish your channel, we would like to share a few words of caution:
Прежде чем вы крикнете @emph{Ух-ты, это круто!} и опубликуете собственный канал, необходимо учесть некоторые предостережения:
Before publishing a channel, please consider contributing your package definitions to Guix proper (@pxref{Contributing}). Guix as a project is open to free software of all sorts, and packages in Guix proper are readily available to all Guix users and benefit from the project's quality assurance process.
Перед публикацией канала, пожалуйста, рассмотрите возможность поделиться вашими определениями пакетов со сборником Guix (@pxref{Contributing}). Guix, как проект, открыт свободному программному обеспечению любого назначения, и пакеты в сборнике Guix готовы и доступны для использования всеми пользователями Guix и прошли проверку качества.
Package modules and package definitions are Scheme code that uses various programming interfaces (APIs). We, Guix developers, never change APIs gratuitously, but we do @emph{not} commit to freezing APIs either. When you maintain package definitions outside Guix, we consider that @emph{the compatibility burden is on you}.
 
Corollary: if you're using an external channel and that channel breaks, please @emph{report the issue to the channel authors}, not to the Guix project.
Вывод: если вы используете внешний канал, и этот канал ломается, пожалуйста, @emph{заявите об этой проблеме авторам каналв}, но не в проект Guix.
You've been warned! Having said this, we believe external channels are a practical way to exert your freedom to augment Guix' package collection and to share your improvements, which are basic tenets of @uref{https://www.gnu.org/philosophy/free-sw.html, free software}. Please email us at @email{guix-devel@@gnu.org} if you'd like to discuss this.
Вы предупреждены! Обозначив это, мы верим, что внешние каналы --- это способ для вас проявлять свою свободу и вместе с тем расширять коллекцию пакетов Guix и делиться улучшениями, что является основными догматами @uref{https://www.gnu.org/philosophy/free-sw.ru.html, свободного программного обеспечения}. Пожалуйста, свяжитесь с нами по e-mail @email{guix-devel@@gnu.org}, если вы хотите обсудить это.
subdirectory, channels
подкаталог, каналы
As a channel author, you may want to keep your channel modules in a sub-directory. If your modules are in the sub-directory @file{guix}, you must add a meta-data file @file{.guix-channel} that contains:
Как автор канала, вы можете хранить модули канала в подкаталоге. Если ваши модули находятся в подкаталоге @file{guix}, вы должны добавить файл метаданных @file{.guix-channel}, который содержит:
(channel
(version 0)
(directory "guix"))
(channel
(version 0)
(directory "guix"))
The modules must be @b{underneath} the specified directory, as the @code{directory} changes Guile's @code{load-path}. For example, if @file{.guix-channel} has @code{(directory "base")}, then a module defined as @code{(define-module (gnu packages fun))} must be located at @code{base/gnu/packages/fun.scm}.
 
Doing this allows for only parts of a repository to be used as a channel, as Guix expects valid Guile modules when pulling. For instance, @command{guix deploy} machine configuration files are not valid Guile modules, and treating them as such would make @command{guix pull} fail.
 
dependencies, channels
зависимости, каналы
meta-data, channels
метаданные, каналы
Channel authors may decide to augment a package collection provided by other channels. They can declare their channel to be dependent on other channels in a meta-data file @file{.guix-channel}, which is to be placed in the root of the channel repository.
Авторы канала могут решить расширить коллекцию пакетов пакетами, которые поставляются другими каналами. Они могут объявить, что их канал зависит от других каналов, в файле метаданных @file{.guix-channel}, который нужно разместить в корне репозитория канала.
The meta-data file should contain a simple S-expression like this:
Файл метаданных должен содержать простое выражение S-expression как это:
(channel
(version 0)
(dependencies
(channel
(name some-collection)
(url "https://example.org/first-collection.git")

(channel
(version 0)
(dependencies
(channel
(name 'some-collection)
(url "https://example.org/first-collection.git")

Loading…

User avatar None

String updated in the repository
Warning
ПредупреждеВнимание
5 months ago
User avatar a-chepugov

Suggestion accepted
Warning
ВнимаПредупреждение
5 months ago
Browse all string changes

Things to check

Inconsistent

This string has more than one translation in this project or is untranslated in some components.

Reset

Glossary

English Russian
No related strings found in the glossary.

6491438 String information

Source string description
type: quotation
Flags
no-wrap
Source string location
guix-git/doc/guix.texi:5615 • guix-git/doc/guix.texi:7058 • guix-git/doc/guix.texi:7098 • guix-git/doc/guix.texi:7126 • guix-git/doc/guix.texi:13571 • guix-git/doc/guix.texi:17772 • guix-git/doc/guix.texi:26285 • guix-git/doc/guix.texi:26292 • guix-git/doc/guix.texi:34374 • guix-git/doc/guix.texi:40611 • guix-git/doc/guix.texi:42346
String age
4 years ago
Last updated
22 hours ago
Source string age
4 years ago
Translation file
po/doc/guix-manual.ru.po, string 2744