<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
--></style>
</head>
<body class='hmmessage'>
Thanks Daniel, that was quick.<br><br>Change this how?<br><br>Jean.<br><br><br><br><br><br>> Date: Thu, 22 Oct 2009 09:59:27 -0700<br>> From: dantti85-pk@yahoo.com.br<br>> To: packagekit@lists.freedesktop.org<br>> Subject: Re: [packagekit] Debconf and PackageKit Was Re: Packagekit and Ubuntu<br>> <br>> Yes,<br>> It has been there for a long time,<br>> but hopefully in a few days the new<br>> dbus frontend will change this.<br>> <br>> Daniel.<br>> <br>> <br>> ><br>> >De: Jean Hubbard<br>> >Assunto: Re: [packagekit] Debconf and PackageKit Was Re: Packagekit and Ubuntu<br>> ><br>> > > ><br>> >Has non-interactive debconf support been in PK for sometime or is this new in the 0.5 series?<br>> ><br>> ><br>> ><br>> ><br>> ><br>> >> Date: Fri, 25 Sep 2009 08:35:19 +0100<br>> >> From: hughsient@gmail.com<br>> >> To: packagekit@lists.freedesktop.org<br>> >> Subject: Re: [packagekit] Debconf and PackageKit Was Re: Packagekit and Ubuntu<br>> >> <br>> >> 2009/9/24 Sebastian Heinlein <sebi@glatzor.de>:<br>> >> > I have made up this plan to integrate debconf and conf file conflicts<br>> >> > into PackageKit. These issues will be handled during a running<br>> >> > transaction which will paused while waiting for an answer from the<br>> >> > user - new transaction will be blocked so long. To avoid an endless<br>> >> > block the caller-active property and a time out will be used.<br>> >> <br>> >> If that's what we have to do, that's what we have to do. I can't say I<br>> >> like it, but if we can run things un-attended, ten it doesn't break<br>> >> too many of the use cases.<br>> >> <br>> >> > If the backend recognizes a conf file conflict, pauses the transaction<br>> >> > and reports this to the packagekit daemon. The daemon checks if the<br>> >> > caller is still active. If so it sends a ConfigFileConlift signal with<br>> >> > the old and new file as attributes. The user would call a<br>> >> > ResolveConfigFileConflict method with the new file or possible<br>> >> > predefined values like "keep" or "replace". The daemon sends the<br>> >> > answer to the backend.<br>> >> <br>> >> Sounds sane.<br>> >> <br>> >> > If the caller is no longer available on the bus the daemon will report<br>> >> > this to the backend, which will choose a default action.<br>> >> <br>> >> Doesn't the backend know if the caller is active or not?<br>> >> <br>> >> > Would be basically the same as for config file conflicts. We could<br>> >> > use the proxy debconf frontend. This allows to communicate with<br>> >> > debconf using a socket. The backend would listen on the socket and<br>> >> > behave like a normal debconf frontend. A configuration question would<br>> >> > be send to the backend and from the daemon to the user using a signal.<br>> >> > The signal would need some further thinking since there are different<br>> >> > kind of possible questions e.g. yes/no, lists. See above for answer and<br>> >> > caller-active handling.<br>> >> <br>> >> Right.<br>> >> <br>> >> > A further issue is the communication with the backend. Currently we<br>> >> > cannot access the caller-active property from a spawned backend.<br>> >> > Should we send this information to the backend or limit this advanced<br>> >> > features to native backends?<br>> >> <br>> >> There's no reason why we can't proxy this, the problem is that<br>> >> typically we set the data as environment variables (NETWORK etc) which<br>> >> don't change during the transaction. I'm not sure if you can change an<br>> >> running process' environment. Other ways to contact the running<br>> >> instance is just to dump more stuff to stdin, but if it's like the yum<br>> >> backend it's blocking whilst it's running to command.<br>> >> <br>> >> Either way, I think it's best if the backend itself knows if the<br>> >> caller is active or not.<br>> >> <br>> >> Richard.<br>> >> <br>> >> p.s. Thanks for working on this.<br>> >> _______________________________________________<br>> >> PackageKit mailing list<br>> >> PackageKit@lists.freedesktop.org<br>> >> http://lists.freedesktop.org/mailman/listinfo/packagekit<br>> ><br>> >________________________________<br>> New Windows 7: Simplify what you do everyday. Find the right PC for you.<br>> <br>> <br>> ____________________________________________________________________________________<br>> Veja quais são os assuntos do momento no Yahoo! +Buscados<br>> http://br.maisbuscados.yahoo.com<br>> _______________________________________________<br>> PackageKit mailing list<br>> PackageKit@lists.freedesktop.org<br>> http://lists.freedesktop.org/mailman/listinfo/packagekit<br> <br /><hr />New Windows 7: Find the right PC for you. <a href='http://windows.microsoft.com/shop' target='_new'>Learn more.</a></body>
</html>