On Wed, Mar 19, 2008 at 03:54:20PM -0400, seth vidal wrote: > > On Wed, 2008-03-19 at 14:47 -0500, Michael E Brown wrote: > > On Wed, Mar 19, 2008 at 12:21:38PM -0400, Robin Norwood wrote: > > > On Mon, 17 Mar 2008 21:57:48 +0000 > > > Richard Hughes <hughsient@xxxxxxxxx> wrote: > > > > > > > On Mon, 2008-03-17 at 16:47 -0500, Michael E Brown wrote: > > > > > Firmware-tools uses this *extensively*. I would like to port > > > > > firmware-tools to use package-kit, but can't really, without this > > > > > function. (As opposed to maintaining instructions for apt, yum, > > > > > smart, rug, et al. currently.) > > > > > > > > I've merged in a WhatProvides() abstract method into packagekit a few > > > > minutes ago. I'll add an example as pk-install-depends now, and also > > > > make pkcon fall back if there was no package match with pkcon. > > > > > > > > This means pkcon install $random_provide should work as you wish. > > > > > > Just to clarify, this is in the development version in git, not (yet) > > > in the version in Fedora. > > > > Random package kit question: > > > > Does package kit provide a generic method to set up a yum repository? > > (obviously only applicable for RPM-based systems). Right now that is > > another one of my pain points: setting up repositories across > > suse/fedora/red hat, et al is not possible in a generic way even though > > they all support yum repositories. > > how do you mean 'setup'. All of the above distros use createrepo to > setup a repo. > > or do you mean setup in the package mgmt software, sense? I mean setup in the package mgmt software sense. As in setting up yum to pull from a repo. I'm wondering if it is in-scope for package kit to provide a backend-independent way of setting up the client side. -- Michael -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
