On Mon, Jan 28, 2013 at 7:19 PM, Christophe Fergeau <cfergeau@xxxxxxxxxx> wrote: > On Mon, Jan 28, 2013 at 05:45:25PM +0200, Zeeshan Ali (Khattak) wrote: >> On Mon, Jan 28, 2013 at 3:14 PM, Christophe Fergeau <cfergeau@xxxxxxxxxx> wrote: >> > You can't expect every possible Windows exe file to honour the /S switch. >> >> If a binary doesn't support '/S' switch, it will ignore it? > > Or fail saying it's an unknown parameter? According to Vmware docs, this is a standard MSI option: http://pubs.vmware.com/view-50/index.jsp?topic=/com.vmware.view.installation.doc/GUID-F19EBDF6-20A3-4A8B-95AE-786CC74F26AF.html If that is the case, its supposed to be guaranteed on every windows installer setup app? >> > I'd tend to go with a list of files + a .cmd file which contains the actual >> > commands to run (osinfo-*.cmd would be even better but I'm not 100% sure >> > Windows accept such wildcards). >> > This would let us handle .msi file, unpacked drivers should be possible too >> > with an appropriate .cmd file, ... >> >> This would mean that either us or the driver setup distributor will >> have to provide a cmd file with it? > > Yup, but we currently only have a single binary to support, and there is > already a need for a flag, so we need a way to support this in a more > flexible way than hardcoding it in libosinfo imo. I'd want to avoid hardcoding as well but at the same time I would hate to ask driver distributors (or anyone who wants to add drivers to db in future) to have to write a .cmd file per driver so I'll first want to know if we are worrying for a good reason. -- Regards, Zeeshan Ali (Khattak) FSF member#5124 _______________________________________________ Libosinfo mailing list Libosinfo@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libosinfo
