Eucalyptus

[Garrett Holmstrom]

On Mon, Feb 8, 2010 at 5:29 PM, graziano obertelli
<graziano at eucalyptus.com> wrote:
> As mentioned before, we already have a spec file, which produces packages
> not good enough to be integrated in Fedora, but this will give us a head
> start to flushing out the installation procedure on Fedora as well as
> finding how to configure it properly. I would love for comments on how to
> make things better on Fedora, and in order to do that, we have a source
> tree available on launchpad for 1.6.2. Problem is that, for now, I'll be
> working on a private branch which I'll merge if our Q&A will give the
> green light on the packages: if there is interests in seeing it, I'm more
> than happy to publish it where is convenient for Fedora. Is there interest
> for it? Is there a preference of where to put the code?
>
> Also, if someone is working on axis2c, axis2 and/or rampartc, I'll be more
> than happy to use those packages too.

Before you release 1.6.2, please fix the download URL in the spec
file, which currently leads to a 404 on a domain parking page.  If you
don't plan on making the one that's already there work, perhaps you
could specify http://eucalyptussoftware.com/downloads/releases/eucalyptus-%{version}-src.tar.gz
instead.

Here are some nitpicky packaging guideline-related things that stick out to me:

 * Download URL is incorrect (see comments above)
 * Explicit Conflict tags are forbidden by the packaging guidelines
 * Dependencies need to go in separate packages
     * Fedora's installing files in /opt is forbidden by FHS (see
       https://www.redhat.com/archives/fedora-devel-list/2008-October/msg02291.html)
 * "BuildRequires: java-sdk >= 1.6.0" should be
   "BuildRequires: java-devel >= 1:1.6.0"
 * Should use %configure macro instead of calling configure directly
    * configure is also currently called with the wrong prefix
 * Should use %_sbindir, %_sysconfdir, %_datadir, etc. instead of hardcoding all
   file paths
 * The previously-mentioned Xen vs. KVM config issue (Perhaps a variable at the
   top of the spec file (e.g., "%global hypervisor kvm"))
 * Services should be started/stopped with /sbin/service in %pre
 * Custom variables at the top should be defined with "%global"
 * Custom variables should not begin with "__"
 * Vendor and Icon RPM tags also need to go
 * "This package contains walrus" is not a useful Description
 * Please use one of the approved formats for changelogs:
   https://fedoraproject.org/wiki/Packaging/Guidelines#Changelogs

While I haven't done an in-depth check of things like making sure the
right file types are in the right places and such, hopefully that will
help with getting the spec file cleaned up.  I especially recommend
having a look at https://fedoraproject.org/wiki/Packaging:Java for
tips on packaging Java programs.