Le 02/02/2016 04:39, Simon Wise a écrit :
so looking at apt.conf I see as the very first text 'DESCRIPTION'

/etc/apt/apt.conf is the main configuration file shared by all
       the tools in the APT suite of tools, though it is by no means
       the only place options can be set. The suite also shares a
       common command line parser to provide a uniform environment.

       When an APT tool starts up it will read the configuration
       files in the following order:

        1. the file specified by the APT_CONFIG environment variable
           (if any)

        2. all files in Dir::Etc::Parts in alphanumeric ascending
           order which have either no or "conf" as filename extension
           and which only contain alphanumeric, hyphen (-),
           underscore (_) and period (.) characters. Otherwise APT
           will print a notice that it has ignored a file, unless
           that file matches a pattern in the
           Dir::Ignore-Files-Silently configuration list - in which
           case it will be silently ignored.

        3. the main configuration file specified by Dir::Etc::main

        4. the command line options are applied to override the
           configuration directives or to load even more
           configuration files.


Dir::Etc::Parts is in fact apt.conf.d/

as seen by going to the FILES section at the end of the manpage, either with a search for Dir::Etc::Parts or because you know a FILES section usually exists:

FILES
       /etc/apt/apt.conf
           APT configuration file. Configuration Item:
           Dir::Etc::Main.

/etc/apt/apt.conf.d/
           APT configuration file fragments. Configuration Item:
           Dir::Etc::Parts.

This is also in man apt.conf, but - call me an idiot - I still can't make sense of it. What the hell is the meaning of the words 'Dir', 'Etc', 'Main' and 'Parts'? Why the hell do '::' translate to '/' ? What document did you learn that "language" from?

Another point: I'd expect the configuration tool to provide a way to specify a scope for any parameter setting, something which could, for example, restrict the scope of the line 'APT::Install-Recommends "false";' to synaptic, eg simply 'SYNAPTIC::Install-Recommends "false";'

Maybe, since Synaptic is a front-end to apt, the rationale is it is also intended to tune apt proper. I admit it makes sense. It's imperfect because the setting is lost if you purge synaptic but nothing can be perfect.

    Didier

_______________________________________________
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Reply via email to