The really tricky problem is when a package must modify an existing shared resource. Such as appending lines to an existing config for example.
This is currently solved by having applications support both a config file and a config.d directory. The primary owner (package) of the resource modifies the conf file, while secondary packages drop their own config in conf.d/${package}. Numerous examples exist: logrotate, rsyslog, apache, nginx, systemd and apt come to mind.
Re:Windows Sandbox
by AsyncAwait on Wednesday December 19, 2018 @05:38AM
(#18714707)
> The really tricky problem is when a package must modify an existing shared resource. Such as appending lines to an existing config for example.
Pacman creates a .pacnew file and lets you merge it yourself for this very reason.
Seems like that is offloading the tricky bit to the user rather than solving the tricky problem to be honest.
Yeah that's exactly what's happening. But Arch is an intentionally hands on distro (eg it doesn't even ship a an installer - instead you're expected to do everything yourself via the command line).
Obviously this wouldn't be to everyone's tastes but it's good that market is catered in my opinion (but then I would say that as I'm very much a hands on person).
Re:Windows Sandbox
by AsyncAwait on Wednesday December 19, 2018 @09:08AM
(#18715667)
Yeah, but it's very transparent to the user, which is kind of the Arch Way, and to be fair, there are tools to help you, like pacdiff.
The really tricky problem is when a package must modify an existing shared resource. Such as appending lines to an existing config for example.