diff options
| author | David Kalnischkies <david@kalnischkies.de> | 2015-10-28 14:38:49 +0100 |
|---|---|---|
| committer | David Kalnischkies <david@kalnischkies.de> | 2015-11-04 18:42:27 +0100 |
| commit | 1dd20368486820efb6ef4476ad739e967174bec4 (patch) | |
| tree | e47f748b70975ab3fadd5c10734156346b172e5e /doc/apt-ftparchive.1.xml | |
| parent | e2ea6b63d333e6999d855a026a005726067c38ac (diff) | |
support arch:all data e.g. in separate Packages file
Based on a discussion with Niels Thykier who asked for Contents-all this
implements apt trying for all architecture dependent files to get a file
for the architecture all, which is treated internally now as an official
architecture which is always around (like native). This way arch:all
data can be shared instead of duplicated for each architecture requiring
the user to download the same information again and again.
There is one problem however: In Debian there is already a binary-all/
Packages file, but the binary-any files still include arch:all packages,
so that downloading this file now would be a waste of time, bandwidth
and diskspace. We therefore need a way to decide if it makes sense to
download the all file for Packages in Debian or not. The obvious answer
would be a special flag in the Release file indicating this, which would
need to default to 'no' and every reasonable repository would override
it to 'yes' in a few years time, but the flag would be there "forever".
Looking closer at a Release file we see the field "Architectures", which
doesn't include 'all' at the moment. With the idea outlined above that
'all' is a "proper" architecture now, we interpret this field as being
authoritative in declaring which architectures are supported by this
repository. If it says 'all', apt will try to get all, if not it will be
skipped. This gives us another interesting feature: If I configure a
source to download armel and mips, but it declares it supports only
armel apt will now print a notice saying as much. Previously this was a
very cryptic failure. If on the other hand the repository supports mips,
too, but for some reason doesn't ship mips packages at the moment, this
'missing' file is silently ignored (= that is the same as the repository
including an empty file).
The Architectures field isn't mandatory through, so if it isn't there,
we assume that every architecture is supported by this repository, which
skips the arch:all if not listed in the release file.
Diffstat (limited to 'doc/apt-ftparchive.1.xml')
| -rw-r--r-- | doc/apt-ftparchive.1.xml | 12 |
1 files changed, 8 insertions, 4 deletions
diff --git a/doc/apt-ftparchive.1.xml b/doc/apt-ftparchive.1.xml index 5b2cd83e8..edebb0808 100644 --- a/doc/apt-ftparchive.1.xml +++ b/doc/apt-ftparchive.1.xml @@ -368,9 +368,13 @@ for i in Sections do <varlistentry><term><option>Architectures</option></term> <listitem><para> - This is a space separated list of all the - architectures that appear under search section. The special architecture - 'source' is used to indicate that this tree has a source archive.</para></listitem> + This is a space separated list of all the architectures that appear under + search section. The special architecture 'source' is used to indicate + that this tree has a source archive. The architecture 'all' signals that + architecture specific files like <filename>Packages</filename> should not + include information about architecture <literal>all</literal> packages in + all files as they will be available in a dedicated file. + </para></listitem> </varlistentry> <varlistentry><term><option>LongDescription</option></term> @@ -589,7 +593,7 @@ for i in Sections do </varlistentry> &apt-commonoptions; - + </variablelist> </refsect1> |