it exists and it's called conary rollback
|
| Author | Content |
|---|---|
| devnet Aug 15, 2010 11:54 PM EDT |
it's called rollback You use it with the Conary package manager. The only problem is that it's different and doesn't feel 'normal' so not as many people use it despite its absolute superiority over all other package managers. |
| gus3 Aug 16, 2010 12:17 AM EDT |
Actually, that sounds like exactly the purpose Btrfs was designed for. |
| chalbersma Aug 16, 2010 9:06 PM EDT |
In other words what ZFS does? |
| gus3 Aug 16, 2010 9:13 PM EDT |
Only outside the GPL, chalb. |
| jezuch Aug 17, 2010 2:37 AM EDT |
In other words, snapshotting? (Much, much older concept than both btrfs and ZFS.) |
| Sander_Marechal Aug 17, 2010 3:32 AM EDT |
Yup. Wasn't Fedora or some such distro working on intergrating filesystem snapshots and rollbacks into it's package management system? I can't remember it, nor find it in the newswire. |
| devnet Aug 17, 2010 12:35 PM EDT |
ZFS rolls back a hard drive to a previous state...not invididual packages. Completely different from what the article is looking for and completely different from Conary. Conary rolls back 'changeset' packages much like rolling back changesets on SVN, git, or mercurial would do...because it blends package management and version control. You can also do many of the things you could do using version control like clone, merge, and branch. However, unlike ZFS, you do this on an individual package/component level. |
| DarrenR114 Aug 17, 2010 2:59 PM EDT |
Sander is correct. Fedora uses the YUM/RPM package management ... and there is a rollback feature (since at least 2006): http://blog.chris.tylers.info/index.php?/archives/17-How-to-... |
| bigg Aug 17, 2010 3:50 PM EDT |
Arch's pacman will do it. The catch is that Arch is a rolling release distro, so you need to have saved copies of all previous packages locally, including dependencies, in order to do it. As a Slackware user there is never a need to go back, everything works perfectly the first time. |
| jdixon Aug 17, 2010 4:09 PM EDT |
> As a Slackware user there is never a need to go back, everything works perfectly the first time. Well, unless you're running current. There has been the occasional problem there. But since Slackware packages don't include dependencies and are self contained, rolling back is almost always merely a matter of removing the new package and reinstalling the old one. |
| mbaehrlxer Aug 17, 2011 1:18 AM EDT |
gus3: the conary license was changed to GPLv3 today: http://hg.rpath.com/conary-2.3/rev/ceb203109612 |
Posting in this forum is limited to members of the group: [ForumMods, SITEADMINS, MEMBERS.]
Becoming a member of LXer is easy and free. Join Us!