guix/documentation-cookbook — Russian @ Fedora Weblate: build-system

Zen

	English	Russian	Actions
	The following tutorial covers all the basics around package creation with Guix. It does not assume much knowledge of the Guix system nor of the Lisp language. The reader is only expected to be familiar with the command line and to have some basic programming knowledge.
	The ``Defining Packages'' section of the manual introduces the basics of Guix packaging (@pxref{Defining Packages,,, guix, GNU Guix Reference Manual}). In the following section, we will partly go over those basics again.
	GNU@tie{}Hello is a dummy project that serves as an idiomatic example for packaging. It uses the GNU build system (@code{./configure && make && make install}). Guix already provides a package definition which is a perfect example to start with. You can look up its declaration with @code{guix edit hello} from the command line. Let's see how it looks:
	(define-public hello (package (name "hello") (version "2.10") (source (origin (method url-fetch) (uri (string-append "mirror://gnu/hello/hello-" version ".tar.gz")) (sha256 (base32 "0ssi1wpaf7plaswqqjwigppsg5fyh99vdlb9kzl7c9lng89ndq1i")))) (build-system gnu-build-system) (synopsis "Hello, GNU world: An example GNU package") (description "GNU Hello prints the message \"Hello, world!\" and then exits. It serves as an example of standard GNU coding practices. As such, it supports command-line arguments, multiple languages, and so on.") (home-page "https://www.gnu.org/software/hello/") (license gpl3+)))
	As you can see, most of it is rather straightforward. But let's review the fields together:
	name	name
	The project name. Using Scheme conventions, we prefer to keep it lower case, without underscore and using dash-separated words.
	source	source
	This field contains a description of the source code origin. The @code{origin} record contains these fields:
	The method, here @code{url-fetch} to download via HTTP/FTP, but other methods
	exist, such as @code{git-fetch} for Git repositories.
	The URI, which is typically some @code{https://} location for @code{url-fetch}. Here
	the special `mirror://gnu` refers to a set of well known locations, all of which can be used by Guix to fetch the source, should some of them fail.
	The @code{sha256} checksum of the requested file. This is essential to ensure
	the source is not corrupted. Note that Guix works with base32 strings, hence the call to the @code{base32} function.
	build-system	build-system
	This is where the power of abstraction provided by the Scheme language really shines: in this case, the @code{gnu-build-system} abstracts away the famous @code{./configure && make && make install} shell invocations. Other build systems include the @code{trivial-build-system} which does not do anything and requires from the packager to program all the build steps, the @code{python-build-system}, the @code{emacs-build-system}, and many more (@pxref{Build Systems,,, guix, GNU Guix Reference Manual}).
	synopsis
	It should be a concise summary of what the package does. For many packages a tagline from the project's home page can be used as the synopsis.
	description
	Same as for the synopsis, it's fine to re-use the project description from the homepage. Note that Guix uses Texinfo syntax.
	home-page
	Use HTTPS if available.
	license
	See @code{guix/licenses.scm} in the project source for a full list of available licenses.
	Time to build our first package! Nothing fancy here for now: we will stick to a dummy @code{my-hello}, a copy of the above declaration.
	As with the ritualistic ``Hello World'' taught with most programming languages, this will possibly be the most ``manual'' approach. We will work out an ideal setup later; for now we will go the simplest route.
	Save the following to a file @file{my-hello.scm}.
	(use-modules (guix packages) (guix download) (guix build-system gnu) (guix licenses))
	(package (name "my-hello") (version "2.10") (source (origin (method url-fetch) (uri (string-append "mirror://gnu/hello/hello-" version ".tar.gz")) (sha256 (base32 "0ssi1wpaf7plaswqqjwigppsg5fyh99vdlb9kzl7c9lng89ndq1i")))) (build-system gnu-build-system) (synopsis "Hello, Guix world: An example custom Guix package") (description "GNU Hello prints the message \"Hello, world!\" and then exits. It serves as an example of standard GNU coding practices. As such, it supports command-line arguments, multiple languages, and so on.") (home-page "https://www.gnu.org/software/hello/") (license gpl3+))
	We will explain the extra code in a moment.

Loading…

a-chepugov Suggestion removed guix documentation-cookbook Russian	English build-system Russian 14 characters edited система сборки 2 months ago
a-chepugov Suggestion accepted guix documentation-cookbook Russian	English build-system Russian 12 characters edited Current translation Translated build-system 2 months ago
a-chepugov Suggestion added guix documentation-cookbook Russian	English build-system Russian 12 characters edited Current translation build-system 2 months ago
None Suggestion added guix documentation-cookbook Russian	English build-system Russian 14 characters edited система сборки 3 years 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.

String information

Source string description

type: item

Flags

ignore-same, no-wrap

Source string location

guix-git/doc/guix-cookbook.texi:621

String age

3 years ago

Last updated

2 months ago

Source string age

3 years ago

Translation file

po/doc/guix-cookbook.ru.po, string 216