On Mon, Jan 28, 2013 at 05:27:16PM +0200, Zeeshan Ali (Khattak) wrote: > On Mon, Jan 28, 2013 at 1:01 PM, Christophe Fergeau <cfergeau@xxxxxxxxxx> wrote: > > I think we should still have a way for libosinfo user to have this binary > > run at the end of the install process even though this means having to > > click through a few dialogs. > > Apart from the 3-state (rather than boolean) API I proposed in a > previous mail, we could also have a separate API for adding random > binaries that are put on user's desktop and apps can then use that for > things like these. In this specific case, app will see that there is a > driver available for the os in executable format but script warns on > it during install so they can decide to use this API to add the binary > to the desktop with filename "Installer for X". I don't think this is really useful... And I'd prefer to have the binary be run for me at the end of installation even if it means it's showing dialog. > Such an API could be useful in general and allow us to not complicate > drivers-related API and most importantly not break the concept of > automated/express installation. Depends what you value most, fully unattended install, or some guarantee that the drivers will be installed when the install completes even if this means blocking. While we want the former to be the default, I think it would be nice to have some support for the latter. Christophe
Attachment:
pgpLRrIlQ7iLE.pgp
Description: PGP signature
_______________________________________________ Libosinfo mailing list Libosinfo@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libosinfo
