Gentoo Archives: gentoo-portage-dev

From: Zac Medico <zmedico@g.o>
To: gentoo-portage-dev@l.g.o
Subject: Re: [gentoo-portage-dev] Re: does emerge verify arch compatibility when merging a binary package?
Date: Thu, 23 Apr 2009 17:54:29
In Reply to: Re: [gentoo-portage-dev] Re: does emerge verify arch compatibility when merging a binary package? by Amit Dor-Shifer
2 Hash: SHA1
4 Amit Dor-Shifer wrote:
5 > Following suggestion, I've written a paragraph about the xpak payload. I
6 > think it helps clear things. I think it can be added to the portage(5)
7 > manpage, but would be happy to hear other suggestions.
8 > <BEGIN>
9 > Binary packages
10 > A binary package is an image of a pre-built installation. The merging
11 > process of such a package skipps building from source on the target
12 > host. Portage supports the creation and installation of binary packages.
13 > See emerge(1) for more information.
14 >
15 > A binary package is stored as a .tbz file. Format consists of a bzip2
16 > archive of the installation, with an extra chunk of data appended at the
17 > end. This extra binary data is called the 'xpak' archive (add: origin of
18 > name). It is a binary dump of the package's database entry (under
19 > /var/db/pkg). When a binary package is installed, the xpak payload is
20 > used to generate the entry in the package database. It is also used by
21 > emerge in the installation process (e.g. verifying arch compatibility).
22 > For more information about the format of the xpak archive, see xpak(5).
23 >
24 > Extracting the xpak archive from the .tbz file can be achieved with
25 > qtbz2. Reading the xpak archive can be done using qxpak. See qtbz2(1)
26 > and qxpak(1) for more info.
27 > <END>
28 > Comments, please.
29 > Amit
31 Thanks, I'll add something like this to the portage(5) man page.
32 - --
33 Thanks,
34 Zac
36 Version: GnuPG v2.0.11 (GNU/Linux)
38 iEYEARECAAYFAknwq2IACgkQ/ejvha5XGaOXjQCgqsbXpAi2m/Qy25Fm1VnplgBi
39 Q68AoKPU087TpQBFakpy2Ppx3Gf3WEfw
40 =LQHa
41 -----END PGP SIGNATURE-----