Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=1.2.3 2016-01-14T16:33:58Z 2016-01-14T16:33:58Z David Kalnischkies david@kalnischkies.de 2016-01-14T15:11:28Z urn:sha1:9feb98eb0aeed775f78cb4afbf6bc0e3a90e9fed Git-Dch: Ignore 2015-11-27T15:06:20Z Michael Vogt mvo@ubuntu.com 2015-11-27T15:06:20Z urn:sha1:6257bfdbff8bd15e41b5667a7a10bc123574cb10 2015-11-25T14:20:10Z David Kalnischkies david@kalnischkies.de 2015-11-22T18:02:13Z urn:sha1:ab5b1d0d31b2fbdc4896f8a107611ff056d6a668 Never updating this information is wrong, updating it automatically isn't super correct either, but it seems conventional to have it and updating it more often than needed seems better than updating it never. Git-Dch: Ignore 2015-11-04T17:42:27Z David Kalnischkies david@kalnischkies.de 2015-10-28T13:38:49Z urn:sha1:1dd20368486820efb6ef4476ad739e967174bec4 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. 2015-09-14T13:22:19Z David Kalnischkies david@kalnischkies.de 2015-09-13T15:23:55Z urn:sha1:9e4464914bcc5c896d81f7ca1948f9bfbfb50886 2014-08-26T18:49:48Z David Kalnischkies david@kalnischkies.de 2014-07-18T14:42:40Z urn:sha1:5abbf5bbb5ee8717f89cac6ef409c4cec79259f6 Not all are needed for all files at the moment, but the new docbook building hadn't available some of the entities it used as the files weren't correctly copied around in all cases and having the same across the bord makes working with all of them a little easier. Git-Dch: Ignore 2013-11-30T22:34:15Z David Kalnischkies kalnischkies@gmail.com 2013-11-30T18:15:02Z urn:sha1:694ef56e802bbab94595fc491fdc6ef8b4f525c1 manpages sometimes refer to distro-specific things like the name of the package providing the achive-keyring. Having a central place to configure this helps in having it consistent in the manpages and allows to load this info from other places in the buildsystem as well later. 2012-06-09T21:08:19Z David Kalnischkies kalnischkies@gmail.com 2012-06-09T21:08:19Z urn:sha1:3adddfa810c916132b59b11c736e8747581662bc - default to putting the Contents-* files below $(SECTION) as apt-file expects them there - thanks Martin-Éric Racine! (Closes: #675827) 2012-06-09T20:05:55Z David Kalnischkies kalnischkies@gmail.com 2012-06-09T20:05:55Z urn:sha1:dabb215cb8c4b074d286737da523d8ef14381468 2012-06-06T22:04:44Z Justin B Rye jbr@edlug.org.uk 2012-06-06T22:04:44Z urn:sha1:14301cf38d3a211250589da1f8ad1d89e4721bfa - review and fix typo, grammar and style issues