4 ms·
> Of course you still have the problem of the software writing files during its operation but that should be limited to $HOME (on POSIX systems) or any path tha
by alkonaut 8y ago
> Of course you still have the problem of the software writing files during its operation but that should be limited to $HOME (on POSIX systems) or any path that is writable by the owner / group of the user that application runs as (which should be limited even if it’s a system service).
The really tricky problem is when a package must modify an existing shared resource. Such as appending lines to an existing config for example.
- AsyncAwait 8y ago> 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.
- alkonaut 8y agoSeems like that is offloading the tricky bit to the user rather than solving the tricky problem to be honest.
- laumars 8y agoYeah 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).
- AsyncAwait 8y agoYeah, 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.
- tremon 8y agoThe 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.