- Site menu:
- Latest Discussions
- Latest Newswire
- Archives
- Submit Story
- Story HOWTO
- Syndicate
- E-mail Alerts
Tales From the Front: in Search of APT-GET UNDO
|
|
|
Comments (11)
Actually, that sounds like exactly the purpose Btrfs was designed for.
In other words what ZFS does?
Only outside the GPL, chalb.
In other words, snapshotting? (Much, much older concept than both btrfs and ZFS.)
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.
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.
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.
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-...
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-...
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.
> 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.
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.
gus3: the conary license was changed to GPLv3 today: http://hg.rpath.com/conary-2.3/rev/ceb203109612
Post a comment
A free account is needed to post. Write your comment here first: your text is kept in this browser while you sign up or log in, and is waiting for you when you come back.
Your message:Markdown: **bold**, *italic*, [text](https://link), - lists, > quotes, $x^2$ for math. Formatting help
Sign up and post (it is free) or Log in and post
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.