https://bugzilla.novell.com/show_bug.cgi?id=830002 https://bugzilla.novell.com/show_bug.cgi?id=830002#c2 --- Comment #2 from Bruce Rogers <brogers@suse.com> 2013-07-31 22:15:40 UTC --- Just an update - As I was hoping to get something checked in for M4 of openSUSE 13.1, I now want to take a less hurried approach here, as it seems that there are many factors that need to be worked through to make sure we are doing this the right way. Some concerns are: * What is the best way to ensure we are tracking correctly the firmware versions needed by QEMU (and possibly Xen) * What granularity should be used to provide firmware - one package for all firmware, or one package per tar-ball, etc * for firmware which we can not yet build (and perhaps never will be able to build), what package should deliver that component * It's not really clear what the best way to build firmware for other arch's is. The noarch package with per-arch processing seems to work ok, but if we end up needing in the long run to either do cross compilation, or possibly user-mode emulation to get full coverage of building all firmware components used, then perhaps we'd want to look into consolidating around that solutions from the get go. * Do we draw a line in the sand for some of the much less used target archs (and for which we don't have support in the build service) and just live with not building the firmware for those archs? * It is still unclear if we can correctly identify all the sources needed to build the same firmware as what is provided in the upstream provided binary blobs I'd like to have more of these questions answered before we commit to a specific approach. Let's work towards the openSUSE 13.1 Beta to have the critical issues resolved and to have a solid plan in place for the rest. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.