[Sebastian Heinlein]
> Basically PackageKit is just a common interface and a daemon to handle
> transactions. The work is done by backends. The PackageKit daemon just
> receives the request for a driver and routes it to the backend.
>
> But you also need some client tools: The always running gpk-u
On Wed, Jun 16, 2010 at 11:09:32PM +0200, Josselin Mouette wrote:
> Le mercredi 16 juin 2010 à 21:33 +0200, Petter Reinholdtsen a écrit :
> > > Fedora 13 provides PackageKit to install hardware specific packages
> > > after installation. Perhaps we should extend the discover system to
> > > listen
On Wed, 2010-06-16 at 21:33 +0200, Petter Reinholdtsen wrote:
> [Petter Reinholdtsen]
> > Are there better ways to do this? Anyone willing to work on it?
>
> One alternative would be to move the information out of the
> discover-data package, and into the Packages file instead, similar to
> how I
Le mercredi 16 juin 2010 à 21:33 +0200, Petter Reinholdtsen a écrit :
> > Fedora 13 provides PackageKit to install hardware specific packages
> > after installation. Perhaps we should extend the discover system to
> > listen to DBus events and install hardware packages also after
> > installation?
On Wed, Jun 16, 2010 at 22:23:54 +0200, Petter Reinholdtsen wrote:
> [Julien Cristau]
> > We did something like that in lenny (not in the Packages file, but
> > same basic idea), to get X to choose the right driver. It turns out
> > it's a pain to maintain, and doesn't really work all that well.
[Julien Cristau]
> We did something like that in lenny (not in the Packages file, but
> same basic idea), to get X to choose the right driver. It turns out
> it's a pain to maintain, and doesn't really work all that well.
Why was it a pain to maintain?
I can imagine it is a pain if there is no a
Petter Reinholdtsen writes:
> [Petter Reinholdtsen]
>> Are there better ways to do this? Anyone willing to work on it?
>
> One alternative would be to move the information out of the
> discover-data package, and into the Packages file instead, similar to
> how Iceweasel[1] and Moonlight[2] might
On Wed, Jun 16, 2010 at 21:33:52 +0200, Petter Reinholdtsen wrote:
> The idea I got was to add headers like this to the package supporting
> specific hardware, and use this information to look up the USB and PCI
> ids present in the machine:
>
> Xb-Hardware-Bus-PCI: 1af4:1002
> Xb-Hardware-Bu
[Petter Reinholdtsen]
> Are there better ways to do this? Anyone willing to work on it?
One alternative would be to move the information out of the
discover-data package, and into the Packages file instead, similar to
how Iceweasel[1] and Moonlight[2] might find their plugins and codec
packages,
9 matches
Mail list logo
