Comment 2 for bug 2003759

Revision history for this message
Julian Andres Klode (juliank) wrote :

I think it's better to ship slightly wrong documentation in the wrong place than to ship the right documentation in a language users don't understand, so that's why they don#t get updated in stable releases.

I do not think the apt.conf manual page is a good idea in the first place. These options belong to upgrade commands now, so they should be documented in apt-upgrade once that is written (which houses apt upgrade, apt-get upgrade, apt dist-upgrade, apt full-upgrade, apt-get dist-upgrade docs).

Because the problem is that apt.conf(5) doesn't really have a clear place. Any commandline option can be specified in the config files too, but they're only relevant to their individual commands, so they should be documented alongside their commands. So like apt.conf serves to describe the file format and common options not exposed via command-line flags.

So like if we add a -4 argument corresponding to Acquire::ForceIPv4, it should not be listed in apt.conf anymore as it's in all manual pages that involve downloading, if that makes sense.

And phasing is in apt_preferences because it was implemented using preferences. It no longer is, it's now part of the upgrade code. It certainly does not belong in apt.conf, that's a last resort for stuff we just can't seem to fit in anywhere else.

The whole documentation is horrible.