| |||||||||||||
Another day, another package managerAnother day, another package managerPosted Nov 26, 2012 20:40 UTC (Mon) by vonbrand (subscriber, #4458)In reply to: Another day, another package manager by man_ls Parent article: GNU Guix launches
The real scenario is more like "System works fine (at least it looks that way), user updates something, does random stuff, screws around with some configuration, after boot something is now broken." Roll back what? The update? Which of the 200 package updates since last boot? The configuration change(s)? The changes in other, perhaps (or not) related data? Local configuration in the user's account? As I said, it is definitely never that simple.
(Log in to post comments)
Not the cure for cancer Posted Nov 26, 2012 21:23 UTC (Mon) by man_ls (subscriber, #15091) [Link] Way to be positive, man! At least with a transactional package manager you can roll back the 200 package updates since last boot and discard that factor. Or confirm it; and in that case you can even bisect which package update caused the wreckage.And yes, before you say anything: a transactional package manager will not protect you if robbers come to your house or the CIA confiscates your hard drive or a lightning disintegrates the sodding computer. It is a limited tool with limited uses, which savvy administrators can use to their advantage.
|
|||||||||||||