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? > > > 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. Christophe
Attachment:
pgpOyFmQK5t4s.pgp
Description: PGP signature
_______________________________________________ Libosinfo mailing list Libosinfo@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libosinfo
