On 27.07.22 13:17, [email protected] wrote: > Hi, > >>> So, can we have a specification or a (ranked) requirements list to what >>> the configuration (file) format should actually be able configure, also >>> to not miss something out and to be future-proof to not switch formats >>> again? >>> >> >> In my understanding the basic requirements are "should be able to replace >> bgenv.dat" and "should be configurable in the field, in case something >> goes wrong". But I haven't seen a formalized list yet. > > Needs not to be "formal" but clear in requirements. This is far from it > and doesn't enable me to make an informed decision nor to get into > discussion on this "RfD" thread. > Please elaborate on the requirements/use cases in a more detailed manner. >
I would put it this way: - must be able to model existing variables, including user vars, from bgenv.dat - must be able to add new variables without breaking older implementations (appending new vars, appending new sections of vars) - should be able to signal semantical changes if existing variables (different meaning of values, new possible values, renaming or removal of variables) Jan -- Siemens AG, Technology Competence Center Embedded Linux -- You received this message because you are subscribed to the Google Groups "EFI Boot Guard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/efibootguard-dev/8d0d936a-6165-b722-8b0c-ec332ac62869%40siemens.com.
