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 defaults. That is because defaults change
> > over time, and I don't want things to break when people upgrade to
> > a newer release. Thank you for not blowing away existing config
> > files. You're expected to run "postfix upgrade-configuration"
> > instead.
>
> 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_directory=/usr/lib...
> ...
Why would one want to hard-code /usr/lib?
Why not also override queue_directory, data_directory, etc? Of
course many of these are meaningful only for first-time installs.
> > As for shlib_dir in main.cf:
> >
> > shlib_dir not only specifies at BUILD time the location for
> > libpostfix-*, information that the runtime linker needs to use to
> > start a Postfix program, before any Postfix program can look up
> > settings in main.cf.
You missed the paragraph that immediately follows this. It explains
how the main.cf setting is used during RUN time.
> I feel come confusion here. postconf -d shlib_directory reports
> expected build-time value. Do you mean components that reads
> main.cf directly instead of query to postconf? Presence or absence
> of explicit shlib_directory in main.cf does not help in the case
> of problem with library load paths.
Wietse
