Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=1.1.1 2015-11-04T17:04:05Z 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:04Z David Kalnischkies david@kalnischkies.de 2015-10-26T18:30:44Z urn:sha1:9055d5e68bd09f31df00e45bd14cb599ba3735e5 apt is supposed to be a user-friendly interface, so while these commands are usually poweruser material and therefore do not need to be shown in general introduction manpages/help messages its of no use to not allow users to use them. This includes clean, autoclean, build-dep, source, download, changelog, depends, rdepends and showsrc – it doesn't include more non-interactive commands like dump or xvcg as those are usually used by scripts if at all. Closes: 778234, 780700, 781237 2015-11-04T17:04:04Z David Kalnischkies david@kalnischkies.de 2015-10-26T15:50:21Z urn:sha1:41d39345bdc31cb9b8be057cd678aa2890830437 Git-Dch: Ignore 2015-11-04T17:04:04Z David Kalnischkies david@kalnischkies.de 2015-10-26T10:42:32Z urn:sha1:6079b276a959086ff18302cab752b6d7cfe5ad9f Its not as simple as I initially thought to abstract this enough to make it globally usable, so lets not pollute global namespace with this for now. Git-Dch: Ignore 2015-11-04T17:04:04Z David Kalnischkies david@kalnischkies.de 2015-10-25T22:45:09Z urn:sha1:011188e3920f21e6883c2dab956b3d4fb4e8cbfa This ensures that location strings loaded from a location specified via configuration (Dir::Locale) effect the help messages for commands. Git-Dch: Ignore 2015-11-04T17:04:03Z David Kalnischkies david@kalnischkies.de 2015-10-25T11:35:00Z urn:sha1:2b0660b537581e9e65180e4cf1a94d763fd66847 -q is for logging and -qqq (old -qq) basically kills every output expect errors, so there should be a way of declaring a middleground in which the output of e.g. 'update' isn't as verbose, but still shows some things. The test framework was actually making use of by accident as it ignored the quiet level in output setup for apt before. Eventually we should figure out some better quiet levels for all tools… 2015-11-04T17:04:03Z David Kalnischkies david@kalnischkies.de 2015-10-24T20:43:37Z urn:sha1:e7e10e47476606e3b2274cf66b1e8ea74b236757 All mains pretty much do the same thing, so lets try a little harder to move the common parts into -private to have the real differences more visible. Git-Dch: Ignore 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-09-14T13:22:18Z David Kalnischkies david@kalnischkies.de 2015-09-12T08:15:52Z urn:sha1:7c4f1ca5fe315a8223570b05994d6d7ca7c55c4f A bit unfair that only Bzr had this message. Lets at least print it for git as well with the option of adding more later without string changes. 2015-08-31T09:00:12Z David Kalnischkies david@kalnischkies.de 2015-08-31T09:00:12Z urn:sha1:7c8206bf26b8ef6020b543bbc027305dee8f2308 We had a very similar method previously for our own private usage, but with some generalisation we can move this check into the acquire system proper so that all frontends profit from this compatibility change. As we are disabling a security feature here a warning is issued and frontends are advised to consider reworking their download logic if possible. Note that this is implemented as an all or nothing situation: We can't just (not) drop privileges for a subset of the files in a fetcher, so in case you have to download some files with and some without you need to use two fetchers.