<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> <title></title> </head> <body bgcolor="#ffffff" text="#000000"> Matthias Clasen wrote: <blockquote cite="mid:cbccc63c0810271328t56d58dd4j16385dde3fb5d3d3@mail.gmail.com" type="cite"> <pre wrap="">On Mon, Oct 27, 2008 at 4:16 PM, Rahul Sundaram <a class="moz-txt-link-rfc2396E" href="mailto:sundaram@fedoraproject.org"><sundaram@fedoraproject.org></a> wrote: </pre> <blockquote type="cite"> <pre wrap="">Matthias Clasen wrote: </pre> <blockquote type="cite"> <pre wrap="">Just not true. There is no reason that repos cannot be kept internally consistent at all times. </pre> </blockquote> <pre wrap="">Tools are supposed to deal with the current reality. Not a idealised version of it. Even if theoretically repos can be kept consistent, in practise it isn't always that way. So what is PackageKit going to do about it? </pre> </blockquote> <pre wrap=""> Sure, PK needs to be able to handle the occasional inconsistency, but designing the tool around the current rawhide situation (almost always inconsistent) is just not adequate. </pre> <blockquote type="cite"> <blockquote type="cite"> <pre wrap="">Inconsistencies between multiple repositories are different, and should probably be treated differently, too. </pre> </blockquote> <pre wrap="">How exactly? Majority of users end up using multiple repositories anyway so the situation of a user using just a single repository is mostly irrelevant. </pre> </blockquote> <pre wrap=""> One thing that comes to mind would be to ignore 'additional' repos if they cause conflicts with the 'main' one. </pre> </blockquote> it is not that simple, if you have installed 'bar' from a additional repo there need a 'libfoo.so.1'  (libfoo-1.0) from the main repo.<br> and the lib is bumped to 'libfoo.so.2' (libfoo-2.0), then the transaction will fail until an updated 'bar' there need 'libfoo.so.2' is available.<br> <br> Tim<br> </body> </html>