Package: src:edk2 Version: 0~20160813.de74668f-2 Severity: wishlist Hi!
[0] shows the binary packages currently being built from src:edk2:
* The "ovmf" package contains the build for x64 in
/usr/share/OVMF/OVMF_{CODE,VARS}.fd
* The "qemu-efi" contains the build for aa64
in/usr/share/AAVMF/AAVMF_{CODE,VARS}.fd
Neither the package names nor the file paths seem very intuitive, and
also using upper case is just unnecessary typing work for the user.
This becomes even more important if you try to fix #842683 [1], so I
propose a scheme looking something like this:
* There is only one arch:all package called "ovmf" containing the
builds for all architectures.
* The actual firmware files could be named like this:
/usr/share/ovmf/$arch.$type
where $arch would be the UEFI-style architecture name in lower
case, i.e. "ia32", "x64", "ia64", "arm", "aa64" [2] and $type
would be one of "code", "vars", "unified" (for the deprecated
variant with code and vars in one file).
* Compatibility is ensured by providing a transitional qemu-efi
package depending on the ovmf package and the ovmf package
carrying symlinks for all previously used file paths.
What do you think?
Best regards
Alexander Kurtz
[0] https://packages.debian.org/source/sid/edk2
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842683
[2] http://www.uefi.org/specifications, version 2.6, section 3.5.1.1
signature.asc
Description: This is a digitally signed message part
