On May 11, 2013, at 10:39 PM, Andrey Borzenkov wrote: > В Sat, 11 May 2013 17:07:19 -0700 > Seth Goldberg <seth.goldb...@oracle.com> пишет: > >> Hi, >> >> What about the feature environment variable to allow dynamic detection of >> this enhancement? >> > > That really does not scale. Commands come and go. What about single > command "has" (or probably better "implements") as in
That's what we've had thus far, which is why I'm referring to it. Existing script that has to run regardless of the version of GRUB will continue to need to refer to the existing feature vars. Going forward, I'm OK with your scheme. --S > > implements --command eval|testspeed|... > implements --crypto_algorithm sha256|... > implements --network_protocol http|tftp|ipv6|... > > Command "implements" itself may be instantiated under > fetature_201_final (or whatever next version is). > > It probably could even be extended to feature test of single commands, > like > > implements --command menuentry --feature id > > > Note that in this specific case (eval) this probably is not useful at > all. If you want to test whether this command is present, you > presumably are going to write alternative implementation without eval. > In this case why bother to test in the first place? > > _______________________________________________ > Grub-devel mailing list > Grub-devel@gnu.org > https://lists.gnu.org/mailman/listinfo/grub-devel _______________________________________________ Grub-devel mailing list Grub-devel@gnu.org https://lists.gnu.org/mailman/listinfo/grub-devel
