On 6/4/19 8:56 AM, Thorsten Kukuk wrote:
My impression is, you didn't read my proposal,
else you would know that
a) and b) were investigated deeply.
Admittedly I did not, yet the initial email contained enough for discussion.
In another message, Jan talks about "Regular programs" vs. "Cooperative
I like the idea: many programs could run without a config file, because they
could use their built-in default values ... which should be identical to those
in the config file anyway. E.g. sshd_config doesn't have too many active settings
left because they are identical to the internal defaults; that's good.
But I'd like to point the discussion also another direction.
On my daily-work PCs, there are regularly showing up .rpmnew and .rpmsave files
from packages I certainly never have touched. As an example, this is
'/etc/pulse/client.conf.d/50-system.conf' from the pulseaudio package and
'/etc/speech-dispatcher/speechd.conf' from speech-dispatcher.
Isn't this a simply packaging bug (or a result from an old, already solved bug)?
For me the question is what are the packages which really have this kind
of problem - regularly? For those, approaching upstream to have the default
files separated is fine for me, I only doubt that we can push such changes
effectively with introducing downstream patches. We need to have upstream
in the boat since day one, otherwise downstream patches will wait for
getting applied upstream for ages.
Have a nice day,
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org