Ondřej Vašík wrote:
AFAIK there is no option to ignore files
completely in update, so .rpmnew are created although is always
completely useless (unless you have some script to add missing
users/groups from that .rpmnew file).
I am confused, shouldn't the .rpmnew only get created if the version in
the rpm has changed from what was in the last "successfully installed"
rpm? IOW I should be able to install 1000 updates to the rpm with
/etc/passwd, but as long as the /etc/passwd in the rpm is the same I
should never see a .rpmnew.
(Okay, the changed hashes throw a wrench in this, but that's another
discussion that has already happened.)
I guess we can't expect user to run some merge tool after transaction.
Why not? We already expect them to do something with the .rpmnew. Why
not make "something" easier to do?
It has to be automated somehow.
Automated, unreviewed updates of config files are dangerous :-). It's
technically possible (you could run the merge tool automatically) but I
don't think it's a good idea.
Maybe some separate file with default
users/groups (like existing uidgid file) and something (?cron job) to
periodically check it, if those users/groups do exist on system?
/etc/passwd is actually a case where automatic merge is probably fine
for additions (removal is more dangerous, of course), but I'm thinking
to apply this to config files in general.
--
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
