Difference between revisions of "Makepkg/ru"

== Конфигурация ==

== Конфигурация ==

=== Архитектура, флаги компиляции ===

=== Архитектура, флаги компиляции ===

=== Выходной пакет ===

=== Выходной пакет ===

Next, one can configure where source files and packages should be placed and identify themselves as the packager. This step is optional; packages will be created in the working directory where makepkg is run by default.

Next, one can configure where source files and packages should be placed and identify themselves as the packager. This step is optional; packages will be created in the working directory where makepkg is run by default.

{{hc|/etc/makepkg.conf|<nowiki>

{{hc|/etc/makepkg.conf|<nowiki>

[...]

[...]

#########################################################################

#########################################################################

# PACKAGE OUTPUT

# PACKAGE OUTPUT

#-- Packager: name/email of the person or organization building packages

#-- Packager: name/email of the person or organization building packages

#PACKAGER="John Doe <john@doe.com>"

#PACKAGER="John Doe <john@doe.com>"

[...]

[...]

</nowiki>}}

</nowiki>}}

For example, create the directory:

For example, create the directory:

  $ mkdir /home/$USER/packages

  $ mkdir /home/$USER/packages

Then modify the {{ic|PKGDEST}} variable in {{ic|/etc/makepkg.conf}} accordingly.

Then modify the {{ic|PKGDEST}} variable in {{ic|/etc/makepkg.conf}} accordingly.

The {{ic|PACKAGER}} variable will set the {{ic|packager}} value within compiled packages' {{ic|.PKGINFO}} metadata file. By default, user-compiled packages will display:

The {{ic|PACKAGER}} variable will set the {{ic|packager}} value within compiled packages' {{ic|.PKGINFO}} metadata file. By default, user-compiled packages will display:

{{hc|pacman -Qi package|<nowiki>

{{hc|pacman -Qi package|<nowiki>

[...]

[...]

[...]

[...]

</nowiki>}}

</nowiki>}}

Afterwards:

Afterwards:

{{hc|pacman -Qi package|<nowiki>

{{hc|pacman -Qi package|<nowiki>

[...]

[...]

[...]

[...]

</nowiki>}}

</nowiki>}}

This is useful if multiple users will be compiling packages on a system, or you are otherwise distributing your packages to other users.

This is useful if multiple users will be compiling packages on a system, or you are otherwise distributing your packages to other users.

=== Signature checking ===

=== Signature checking ===

The following procedure is not necessary for compiling with makepkg, for your initial configuration proceed to [[#Usage]]. To temporarily disable signature checking call the makepkg command with the {{ic|--skippgpcheck}} option.

The following procedure is not necessary for compiling with makepkg, for your initial configuration proceed to [[#Usage]]. To temporarily disable signature checking call the makepkg command with the {{ic|--skippgpcheck}} option.

If a signature file in the form of .sig is part of the [[PKGBUILD]] source array, makepkg validates the authenticity of source files. For example, the signature pkgname-pkgver.tar.gz.sig is used to check the integrity of the file pkgname-pkgver.tar.gz with the gpg program. If desired, signatures by other developers can be manually added to the gpg keyring. Look into the [[GnuPG]] article for further information.

If a signature file in the form of .sig is part of the [[PKGBUILD]] source array, makepkg validates the authenticity of source files. For example, the signature pkgname-pkgver.tar.gz.sig is used to check the integrity of the file pkgname-pkgver.tar.gz with the gpg program. If desired, signatures by other developers can be manually added to the gpg keyring. Look into the [[GnuPG]] article for further information.

{{Note|The signature checking implemented in makepkg does not use pacman's keyring. Configure gpg as explained below to allow makepkg reading pacman's keyring.}}

{{Note|The signature checking implemented in makepkg does not use pacman's keyring. Configure gpg as explained below to allow makepkg reading pacman's keyring.}}

The gpg keys are expected to be stored in the user's {{ic|~/.gnupg/pubring.gpg}} file. In case it does not contain the given signature, makepkg shows a warning.

The gpg keys are expected to be stored in the user's {{ic|~/.gnupg/pubring.gpg}} file. In case it does not contain the given signature, makepkg shows a warning.

{{hc|makepkg|<nowiki>

{{hc|makepkg|<nowiki>

</nowiki>}}

</nowiki>}}

When configured as before, the output of {{ic|gpg --list-keys}} contains a list of keyrings and developers. Now makepkg can compile AUR packages submitted by Arch Linux developers with successful signature checking.

When configured as before, the output of {{ic|gpg --list-keys}} contains a list of keyrings and developers. Now makepkg can compile AUR packages submitted by Arch Linux developers with successful signature checking.

== Usage ==

== Usage ==

Before continuing, ensure the "base-devel" group is installed. Packages belonging to this group are not required to be listed as dependencies in [[PKGBUILD]] files. Install the "base-devel" group by issuing (as root):

Before continuing, ensure the "base-devel" group is installed. Packages belonging to this group are not required to be listed as dependencies in [[PKGBUILD]] files. Install the "base-devel" group by issuing (as root):

{{Note|Before complaining about missing (make) dependencies, remember that the "base" group is assumed to be installed on all Manjaro Linux systems. The group "base-devel" is assumed to be installed when building with '''makepkg'''.}}

{{Note|Before complaining about missing (make) dependencies, remember that the "base" group is assumed to be installed on all Manjaro Linux systems. The group "base-devel" is assumed to be installed when building with '''makepkg'''.}}

{{Warning|Only build and/or install packages from trusted sources.}}

{{Warning|Only build and/or install packages from trusted sources.}}

Once in possession of a {{ic|PKGBUILD}}, change to the directory where it is saved and issue the following command to build the package described by said {{ic|PKGBUILD}}:

Once in possession of a {{ic|PKGBUILD}}, change to the directory where it is saved and issue the following command to build the package described by said {{ic|PKGBUILD}}:

  $ makepkg

  $ makepkg

To have makepkg clean out leftover files and folders, such as files extracted to the $srcdir, add the following option. This is useful for multiple builds of the same package or updating the package version, while using the same build folder. It prevents obsolete and remnant files from carrying over to the new builds.

To have makepkg clean out leftover files and folders, such as files extracted to the $srcdir, add the following option. This is useful for multiple builds of the same package or updating the package version, while using the same build folder. It prevents obsolete and remnant files from carrying over to the new builds.

  $ makepkg -c

  $ makepkg -c

If required dependencies are missing, makepkg will issue a warning before failing. To build the package and install needed dependencies automatically, simply use the command:

If required dependencies are missing, makepkg will issue a warning before failing. To build the package and install needed dependencies automatically, simply use the command:

  $ makepkg -s

  $ makepkg -s

Note that these dependencies must be available in the configured repositories; see [[pacman]] for details. Alternatively, one can manually install dependencies prior to building ({{ic|pacman -S --asdeps dep1 dep2}}).

Note that these dependencies must be available in the configured repositories; see [[pacman]] for details. Alternatively, one can manually install dependencies prior to building ({{ic|pacman -S --asdeps dep1 dep2}}).

Once all dependencies are satisfied and the package builds successfully, a package file ({{ic|pkgname-pkgver.pkg.tar.xz}}) will be created in the working directory. To install, run (as root):

Once all dependencies are satisfied and the package builds successfully, a package file ({{ic|pkgname-pkgver.pkg.tar.xz}}) will be created in the working directory. To install, run (as root):

  # pacman -U pkgname-pkgver.pkg.tar.xz

  # pacman -U pkgname-pkgver.pkg.tar.xz

Alternatively, to install, using the {{ic|-i}} flag is an easier way of running {{ic|pacman -U pkgname-pkgver.pkg.tar.xz}}, as in:

Alternatively, to install, using the {{ic|-i}} flag is an easier way of running {{ic|pacman -U pkgname-pkgver.pkg.tar.xz}}, as in:

  $ makepkg -i

  $ makepkg -i

== Tips and Tricks ==

== Tips and Tricks ==

=== Improving compile times ===

=== Improving compile times ===

{{hc|/etc/makepkg.conf|<nowiki>

{{hc|/etc/makepkg.conf|<nowiki>

[...]

[...]

#########################################################################

#########################################################################

# BUILD ENVIRONMENT

# BUILD ENVIRONMENT

#-- Specify a directory for package building.

#-- Specify a directory for package building.

#BUILDDIR=/tmp

#BUILDDIR=/tmp

[...]

[...]

</nowiki>}}

</nowiki>}}

Uncommenting the {{ic|1=BUILDDIR=/tmp}} line and setting it to e.g. {{ic|1=BUILDDIR=/tmp/builds}} (or leaving it to its default value) will make use of Arch default {{ic|/tmp}} [[tmpfs]].

Uncommenting the {{ic|1=BUILDDIR=/tmp}} line and setting it to e.g. {{ic|1=BUILDDIR=/tmp/builds}} (or leaving it to its default value) will make use of Arch default {{ic|/tmp}} [[tmpfs]].

{{Note|The [[tmpfs]] folder needs to be mounted without the {{ic|noexec}} option, else it will prevent build scripts or utilities from being executed. Also, as stated in [[fstab#tmpfs]], its default size is half of the available RAM so you may run out of space.}}

{{Note|The [[tmpfs]] folder needs to be mounted without the {{ic|noexec}} option, else it will prevent build scripts or utilities from being executed. Also, as stated in [[fstab#tmpfs]], its default size is half of the available RAM so you may run out of space.}}

For more information, please refer to [[fstab]] and [[Tmpfs#Improving compile times]].

For more information, please refer to [[fstab]] and [[Tmpfs#Improving compile times]].

=== Generate new md5sums ===

=== Generate new md5sums ===

Since [http://allanmcrae.com/2013/04/pacman-4-1-released/ pacman 4.1] {{ic|makepkg -g >> PKGBUILD}} is no longer required as pacman-contrib was [https://projects.archlinux.org/pacman.git/tree/NEWS merged] along with the {{ic|updpkgsums}} script that will generate new checksums and replace them in the PKGBUILD:

Since [http://allanmcrae.com/2013/04/pacman-4-1-released/ pacman 4.1] {{ic|makepkg -g >> PKGBUILD}} is no longer required as pacman-contrib was [https://projects.archlinux.org/pacman.git/tree/NEWS merged] along with the {{ic|updpkgsums}} script that will generate new checksums and replace them in the PKGBUILD:

  $ updpkgsums

  $ updpkgsums

=== Makepkg source PKGBUILD twice ===

=== Makepkg source PKGBUILD twice ===

Makepkg sources the PKGBUILD twice (once when initially run, and the second time under fakeroot). Any non-standard functions placed in the PKGBUILD will be run twice as well.

Makepkg sources the PKGBUILD twice (once when initially run, and the second time under fakeroot). Any non-standard functions placed in the PKGBUILD will be run twice as well.

=== WARNING: Package contains reference to $srcdir ===

=== WARNING: Package contains reference to $srcdir ===

Somehow, the literal strings {{ic|$srcdir}} or {{ic|$pkgdir}} ended up in one of the installed files in your package.

Somehow, the literal strings {{ic|$srcdir}} or {{ic|$pkgdir}} ended up in one of the installed files in your package.

To identify which files, run the following from the makepkg build directory:

To identify which files, run the following from the makepkg build directory:

  $ grep -R "$(pwd)/src" pkg/

  $ grep -R "$(pwd)/src" pkg/

[http://www.mail-archive.com/arch-general@archlinux.org/msg15561.html Link] to discussion thread.

[http://www.mail-archive.com/arch-general@archlinux.org/msg15561.html Link] to discussion thread.

=== Create uncompressed packages ===

=== Create uncompressed packages ===

If you only want to install packages locally, you can speed up the process by avoiding compression and subsequent decompression. In {{ic|makepkg.conf}}, change {{ic|<nowiki>PKGEXT='.pkg.tar.xz'</nowiki>}} to {{ic|<nowiki>PKGEXT='.pkg.tar'</nowiki>}}.

If you only want to install packages locally, you can speed up the process by avoiding compression and subsequent decompression. In {{ic|makepkg.conf}}, change {{ic|<nowiki>PKGEXT='.pkg.tar.xz'</nowiki>}} to {{ic|<nowiki>PKGEXT='.pkg.tar'</nowiki>}}.

[[Category:Contents Page{{#translation:}}]]

[[Category:Contents Page{{#translation:}}]]