Ondřej Vašík wrote:
do not replace their files on update (as it would have horrible
consequences in the case of file like /etc/passwd and/or /etc/shadow.
Ah... given that users should be running as a normal (!root) account
created at install time, isn't it *guaranteed impossible* to update
/etc/passwd by replacing the old unmodified file with the new?
Here's a pie-in-the-sky idea... store configs as deltas (since at least
~2-4 releases back), write the .rpmnew as always, and notify the user to
run a merge tool after the transaction completes. No more diffing and
merging by hand, except in the face of merge conflicts...
--
Matthew
Please do not quote my e-mail address unobfuscated in message bodies.
--
Microsoft has become the next IBM; a dinosaur struggling to survive in
the age of more able-to-adapt mammals (FLOSS). It remains to be seen if
they'll be able to adapt before they go extinct.
--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list
