Wietse Venema:
> Maxim Nikulin:
>> of shared libraries. If shlib_directory were absent in main.cf
>> and all programs were getting the value from postconf instead of
>> reading main.cf directly than package upgrades would be smooth.
>> Such way is not viable since there are installations
>> with ex
Maxim Nikulin:
> Sorry, I narrowed down context too much, My question was on
> shlib_directory, so I assumed that "..." is a proper substitution
> for all other variables. By the way, I noticed that queue_directory
> and data_directory are passed to "make non-interactive-package"
> but not to "post
On 07.05.2020 20:38, Wietse Venema wrote:
> Maxim Nikulin:
>>
>> Just to avoid any ambiguity, you suggest that package post install
>> script should have something like the following, don't you?
>>
>> postfix upgrade-configuration \
>
> In which script file or documentation file?
>
>> shlib_d
Maxim Nikulin:
> Wietse Venema:
> > Maxim Nikulin:
> >>
> >> I have noticed than postfix-install script explicitly adds
> >> shlib_directory to the main.cf file e.g. during non-interactive install.
> >
> > Postfix records all installation settings in main.cf even if they
> > are at their built-in
Wietse Venema:
> Maxim Nikulin:
>>
>> I have noticed than postfix-install script explicitly adds
>> shlib_directory to the main.cf file e.g. during non-interactive install.
>
> Postfix records all installation settings in main.cf even if they
> are at their built-in defaults. That is because defau
Maxim Nikulin:
> Hi,
>
> I have noticed than postfix-install script explicitly adds
> shlib_directory to the main.cf file e.g. during non-interactive install.
Postfix records all installation settings in main.cf even if they
are at their built-in defaults. That is because defaults change
over tim
