Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=1.1_exp16 2015-11-21T17:04:29Z 2015-11-21T17:04:29Z Justin B Rye justin.byam.rye@gmail.com 2015-11-21T16:50:06Z urn:sha1:d04e44ac8177fc5b70ae0189bb5e437c2502f910 Reference mail: https://lists.debian.org/debian-l10n-english/2015/11/msg00006.html 2015-11-20T08:46:18Z David Kalnischkies david@kalnischkies.de 2015-11-20T08:46:18Z urn:sha1:89497574da3dd40076d955efc936b54e76a8c59c Reported-By: codespell Git-Dch: Ignore 2015-11-19T16:13:56Z David Kalnischkies david@kalnischkies.de 2015-11-19T16:12:32Z urn:sha1:12f7536a66cab673833aeda47be5f2ba44aee8d2 Git-Dch: Ignore 2015-11-19T15:46:29Z Frans Spiesschaert Frans.Spiesschaert@yucom.be 2015-11-19T10:52:44Z urn:sha1:5fba53e44b40aaba1c459c9efb3e73afae3f5a31 Closes: 805474 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-11-04T17:04:05Z David Kalnischkies david@kalnischkies.de 2015-10-27T08:57:26Z urn:sha1:8561c2fedae26aecd8ba758a5e7ef686ba1243f3 The general idea is: A small paragraph on the tool itself as a description, a list of the most used (!= all) commands available in the tool, a remark where to find more information on the tool and its commands (aka: in the manpage) and finally a common block referring to even more manpages. In exchange options are completely omitted from the output as well as deprecated or obscure commands. (Better) Information about them is available in the manpages anyway and the few options which were listed before were also the least interesting ones (-o -c -q and co are hardly of interest for someone totally new looking to find info by asking for help and anyone with a bit of experience doesn't need this short list. Those would need a list of options applying to the command they call, but they are too numerous and command specific to list them sanely in this context. 2015-11-04T17:04:03Z David Kalnischkies david@kalnischkies.de 2015-10-22T14:28:54Z urn:sha1:cbbee23e7768750ca1c8b49bdfbf8a650131bbb6 That is one huge commit with busy work only: Help messages used to be one big translateable string, which is a pain for translators and hard to reuse for us. This change there 'explodes' this single string into new string for each documented string trying hard to split up the translated messages as well. This actually restores many translations as previously adding a single command made all of the bug message fuzzy. The splitup also highlighted that its easy to forget a line, duplicate one and similar stuff. Git-Dch: Ignore 2015-11-04T17:04:02Z David Kalnischkies david@kalnischkies.de 2015-10-20T15:45:35Z urn:sha1:9fd6772b202295d7f643bd94681428c0caffd026 As apt is targetted at users, lets try to make apt(8) for users as well by giving only a quick overview about what is available and some pointers for how to find a whole lot more details. 2015-11-04T17:04:02Z David Kalnischkies david@kalnischkies.de 2015-10-16T16:03:52Z urn:sha1:c3ded84c6f99bda4caf63c8662416ffb0189d31b Especially with apt now, it can be useful to set an option only for apt and not for apt-get. Using a binary-specific subtree which is merged into the root seems like a simple enough trick to achieve this. 2015-11-04T17:04:01Z David Kalnischkies david@kalnischkies.de 2015-10-15T07:35:52Z urn:sha1:002b1bc46b18e9d309d337ddb15a6ccdfb6c9dde The manpage is also slightly updated to work better as a central hub to push people from all angles into the right directions without writting a book disguised as an error message.