Re: Dropping support for rollback?
Andres Vargas - zodman <
zodman@...>
2009-09-03 16:07:13 GMT
yes conary support rollbacks :) its hard to code because internally the actions of conary divide on Jobs
one job can be a set of actions (update/install/remove)
So if i install packagekit
it install packagekit:devel packagekit:runtime as a Job 1
update packagekit:config as a Job 2
So the rollbacks its not remove installed/updated packages its revert a set of jobs what as applied to system. for back to a before state of Job.
Im have understand the rollbacks its controlled by packagekit reverting install/updates packages. Conary not depend from Packagekit for do a rollbacks. Depends of the Set of jobs applied.
I think a feature for support rollbacks not doing for packagekit( send signals, but not do the actions. ) only by the backend will be great.
other stuff is if conary install packages from cli (without help of packagekit) the packagekit database not updated. Because Packagekit its a GUI fronted of conary....
Can code a some plugin for add packagekit integration with conary from conary cli. But its more work its pending.
On Thu, Sep 3, 2009 at 7:46 AM, Mounir Lamouri
<mounir.lamouri-Re5JQEeQqe8@public.gmane.orgm> wrote:
On Thu, Sep 3, 2009 at 2:32 PM, Richard Hughes<
hughsient-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> I don't think any of the backends support rollback, even the conary
> one. There's quite a bit of code in the server and clients to support
> this, but if nothing is going to use it I think it makes sense to rip
> it out. Comments?
can't be something to be used as easily as CTRL+Z (undo/redo). So if
it has to exit it can be something in a menu.
In addition, I don't see a lot of things that should be rollbacked:
installl/remove and enable/disable repository ? In this case, I think
the client can implement that himself. If the user install a package,
he can add in a menu: 'Uninstall foo'. If it has been uninstalled, it
will be'Reinstall foo'. The same thing for repositories.
What do you think about this ? :)
Mounir
<div>
<p>yes conary support rollbacks :) its hard to code because internally the actions of conary divide on Jobs<br><br>one job can be a set of actions (update/install/remove)<br><br>So if i install packagekit<br><br>it install packagekit:devel packagekit:runtime as a Job 1<br>
update packagekit:config as a Job 2<br><br><br>So the rollbacks its not remove installed/updated packages its revert a set of jobs what as applied to system. for back to a before state of Job.<br><br><br>Im have understand the rollbacks its controlled by packagekit reverting install/updates packages. Conary not depend from Packagekit for do a rollbacks. Depends of the Set of jobs applied.<br><br>I think a feature for support rollbacks not doing for packagekit( send signals, but not do the actions. ) only by the backend will be great.<br><br>other stuff is if conary install packages from cli (without help of packagekit) the packagekit database not updated. Because Packagekit its a GUI fronted of conary....<br><br>Can code a some plugin for add packagekit integration with conary from conary cli. But its more work its pending.<br><br><br><br><br></p>
<div class="gmail_quote">On Thu, Sep 3, 2009 at 7:46 AM, Mounir Lamouri <span dir="ltr"><<a href="mailto:mounir.lamouri@...">mounir.lamouri@...m</a>></span> wrote:<br><blockquote class="gmail_quote">
<div class="im">On Thu, Sep 3, 2009 at 2:32 PM, Richard Hughes<<a href="mailto:hughsient@...">hughsient@...</a>> wrote:<br>
> I don't think any of the backends support rollback, even the conary<br>
> one. There's quite a bit of code in the server and clients to support<br>
> this, but if nothing is going to use it I think it makes sense to rip<br>
> it out. Comments?<br><br>
</div>I don't really see the need of rollback for the user. For sure, it<br>
can't be something to be used as easily as CTRL+Z (undo/redo). So if<br>
it has to exit it can be something in a menu.<br>
In addition, I don't see a lot of things that should be rollbacked:<br>
installl/remove and enable/disable repository ? In this case, I think<br>
the client can implement that himself. If the user install a package,<br>
he can add in a menu: 'Uninstall foo'. If it has been uninstalled, it<br>
will be'Reinstall foo'. The same thing for repositories.<br><br>
What do you think about this ? :)<br><br>
Mounir<br><div>
<div></div>
<div class="h5">_______________________________________________<br>
PackageKit mailing list<br><a href="mailto:PackageKit@...">PackageKit@...sktop.org</a><br><a href="http://lists.freedesktop.org/mailman/listinfo/packagekit" target="_blank">http://lists.freedesktop.org/mailman/listinfo/packagekit</a><br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
RSS Feed