On Sat, Aug 17, 2013 at 5:15 PM, Dennis Gilmore <dennis@xxxxxxxx> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Sat, 17 Aug 2013 13:14:14 +0200 > drago01 <drago01@xxxxxxxxx> wrote: > >> On Fri, Aug 16, 2013 at 6:48 AM, Dennis Gilmore <dennis@xxxxxxxx> >> wrote: >> > -----BEGIN PGP SIGNED MESSAGE----- >> > Hash: SHA1 >> > >> > On Mon, 12 Aug 2013 14:47:03 +0100 >> > Richard Hughes <hughsient@xxxxxxxxx> wrote: >> > >> >> Hi all, >> >> >> >> I'd like to ask for comments on a feature I need for the Fedora >> >> Application Installer. The current yum backend in PackageKit does >> >> something like this: >> >> >> >> * yum install foo >> >> * depsolve transaction using cached metadata >> >> * download foo-0.1.noarch.rpm >> >> * error! foo-0.1.noarch.rpm doesn't exist >> >> * download latest repomd, primary >> >> * re-depsolve >> >> * download latest filelists >> >> * continue to re-depsolve >> >> * download foo-0.2.noarch.rpm >> >> * install foo using librpm >> >> >> >> Now, we do this as the metadata is cached on the client side for >> >> up to a week as we don't want to unconditionally update the >> >> metadata for every transaction, but we don't know if we can >> >> download the package without downloading all the metadata >> >> beforehand. This is incompatible with the swish UX in the >> >> application installer where we can search for things straight away >> >> without having "Downloading..." in the UI appearing at odd times. >> >> So my proposal is thus: >> >> >> >> 1. We retain old packages on the mirrors for a minimum of 7 days. >> > >> > without completely rewriting how we compose the trees this is not a >> > possibility. >> >> Bill's mail reads a bit different ... > > I suggest you re-read Bills email. the non-trivial changes are > completely redoing how we compose the trees. Seems like we both have a different definition for the word "complete". -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
