|
Packages are distributed as
gzip-tar
archives of two types.
A
base
archive contains an entire copy of a package and
signifies a major package revision.
A
delta
archive contains updates to portions of a
base
archive and
signifies a minor package revision.
Each file in a
delta
is either removed, created, modified or left unchanged.
delta
archives are read and written by the
ast
pax(1)
command in the
ast-base
package.
package read
reads new packages added to the
$PACKAGEROOT/lib/package/tgz
directory, or packages can be read using the
pax
commands below.
A package archive name reflects its type and contents:
- name.YYYY-MM-DD.tgz
-
A
name
package source base release
YYYY-MM-DD.
The base archive is read by:
pax -rvf name.YYYY-MM-DD.tgz
- name.YYYY-MM-DD.yyyy-mm-dd.tgz
-
A
name
package source delta version
yyyy-mm-dd
of base release
YYYY-MM-DD.
The delta archive is read by:
pax -rvf name.YYYY-MM-DD.yyyy-mm-dd.tgz -z name.YYYY-MM-DD.tgz
- name.YYYY-MM-DD.arch.tgz
-
A
name
package
arch
binary base release
YYYY-MM-DD.
The base archive is read by:
pax -rvf name.YYYY-MM-DD.arch.tgz
- name.YYYY-MM-DD.yyyy-mm-dd.arch.tgz
-
A
name
package
arch
binary delta version
yyyy-mm-dd
of base release
YYYY-MM-DD.
The delta archive is read by:
pax -rvf name.YYYY-MM-DD.yyyy-mm-dd.arch.tgz -z name.YYYY-MM-DD.arch.tgz
Binary
arch
identifiers are of the form
vendor.machine
and are typically less specific than
GNU
config
architecture identifiers.
This is based on the assumption that vendors place value in binary backwards
compatibility.
The source packages have been built on these
architectures.
Binary packages are available for a few popular architectures from this site.
All binaries were generated from the posted source.
|