Re: [kvm-ia64-devel] FW: Follow up - IA64 uses Open Guest Firmware

[Daniel P. B. <ber...@re...>]

On Tue, Apr 01, 2008 at 03:47:10PM +0200, tgi...@fr... wrote:
> My comments inside.
> 
> Quoting "Yang, Fred" <fre...@in...>:
> > Daniel P. Berrange wrote:
> > > When we ship open source software we need to be able to guarentee that
> > > the binary and source code we ship are matching. ie, if someone gets
> > > the
> > > source code, they will be able to build it and get the same result as
> > > the binary we built. This is neccessary for us to comply with the
> > > terms
> > > of licenses such as the GPL. It is also neccessary for our support and
> > > maintainence procedures - if we patch something to fix a bug we need
> > > to
> > > sure that we are building new updated RPM the same way.
> > >
> > > The way we guarentee this is via our RPM build system. Every open
> > > source
> > > package has a source RPM. This is fed into the build system to produce
> > > the binary RPM.  As such, we need to be able to build the binary RPM
> > > using
> > > the tools available in RHEL.   We cannot simply ship a pre-built
> > > binary
> > > and a collection of source code. It has to go via the RPM build
> > > system.
> 
> This is currently a stopper.  We are not able to provide a source package
> that can be build without Java (+ XMLBeans + ... )
> 
> { Note that tianocore is switching to a python based builder so the future is
> open.  But we haven't switched to the new infrastructure.  }

Can you clarify just what parts involve Java. Is it just the build system
which is java based, or is part of the firmware itself coming from java 
source too ? 

I'm wondering whether it would be feasible to try building with GCJ instead
of the Sun/IBM/BEA  JDKs. If only the build system used java this may be
a viable option.

> > > This is not exactly what I meant. In fact, including and distributing
> > > the pre-built binary in the efi-vfirmware.hg would be a violation of
> > > the GPL
> > > because you are not including any of the source from the tiancore.org
> > > Subversion  repository that is used to build it.
> > >
> > > What we require is a single  tar.gz  file containing *all* the source
> > > code neccessary to build the firmware image - this will be a
> > > combination
> > > of the source from efi-vfirmeware.hg, and the neccessary bits from the
> > > tianocore Subversion repository in one tar.gz file. This must *not*
> > > include any pre-built binary images - it must be all source code.
> 
> This is of course doable.  But won't fix point 1.
> 
> Do you do this for xen x86 ?

For x86, the  HVM firmware source code is just part of the regular xen 
released tar.gz and built as part of the userspace build process of Xen.

Regards,
Daniel.
-- 
|: Red Hat, Engineering, Boston   -o-   http://people.redhat.com/berrange/ :|
|: http://libvirt.org  -o-  http://virt-manager.org  -o-  http://ovirt.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505  -o-  F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|