[pkg-eucalyptus-maintainers] [Debian] Re: Eucalyptus 3.1 beta

[graziano obertelli]

Would 2 new targets, something like:

make generate-stub
	(the above would be a dependency for building)
make clean-stubs
	(clean the generated code)

make it easier? Axis2C is not really fast moving: should we just check
in the generated code? Or is it dependent on the
machine/OS/architecture?


On Mon, 2012-06-11 at 14:41 -0400, brian.thomason at gmail.com wrote:
> I generate the code at source package creation time to workaround it,
> but it is far from an elegant solution.  This is the same thing we did
> for the previous Ubuntu/Debian releases.  If we want to be a bit
> sneaky, we could somehow set it up that the code is generated on the
> fly and checked into the repo and rename the dir to something other
> than generated ;-)
> 
> On Mon, Jun 11, 2012 at 2:35 PM, graziano obertelli
> <graziano at eucalyptus.com> wrote:
> > Brian,
> >
> > how did we solve it? A separate repos with the axis2 generated code?
> > Would a separate makefile rule make it simpler to track?
> >
> > cheers
> > graziano
> >
> > On Mon, 2012-06-11 at 11:20 -0400, brian.thomason at gmail.com wrote:
> >> Thanks for jumping in Chris,
> >>
> >> Yes, unfortunately, we are still using the same workaround by
> >> generating the code and placing it in the actual source package. Our
> >> alpha release of the packages can be found here:
> >>
> >> https://launchpad.net/~eucalyptus-maintainers/+archive/ppa/+packages
> >>
> >> -Brian
> >>
> >> On Sun, Jun 10, 2012 at 8:45 PM, Chris Grzegorczyk <grze at eucalyptus.com> wrote:
> >> > Hi Folks,
> >> >
> >> > Long time no say.
> >> >
> >> > Regarding #1:  It continues to be the same short coming we have had w/
> >> > the source since 1.6.2.  The work around we employed in the past was
> >> > to execute the build steps needed to generate the code (which is where
> >> > the axis2 dependency comes up) and then publishing that as the
> >> > upstream tar.gz.  Packaging axis2 or changing the codegen step are
> >> > still huge tasks.
> >> >
> >> > Regarding #2:  This step (which used to be a wget of cloud-lib.tar.gz)
> >> > will be skipped by the clc/Makefile if lib/bcprov.jar is present --
> >> > thus, as we did in the past, the rules need to link the build-deps
> >> > into clc/lib
> >> >
> >> > best regards.
> >> > chris
> >> >
> >> >
> >> >
> >> > On Sun, Jun 10, 2012 at 11:00 AM, Steffen Möller <steffen_moeller at gmx.de> wrote:
> >> >> On 06/10/2012 07:00 PM, Rudy Godoy Guillén wrote:
> >> >>> Hello,
> >> >>>
> >> >>> On Sun, Jun 10, 2012 at 7:06 AM, Charles Plessy <plessy at debian.org> wrote:
> >> >>>> Le Thu, Jun 07, 2012 at 01:42:35AM -0500, Rudy Godoy a écrit :
> >> >>>>> Hello, as you know there's a 3.1 (beta) version now available on github.
> >> >>>>> I've been testing our build system with it and it works with minor changes
> >> >>>>> and issues that I've been fixing, and commiting.
> >> >>>>>
> >> >>>>> Now, there are few things that need further discussion.
> >> >>>>>
> >> >>>>> 1- Axis2 Java
> >> >>>>> The Java lib is a build-dep but it is not in the repo. INSTALL instructs to
> >> >>>>> download from Apache.org's servers. Policy doesn't allow such behavior, so
> >> >>>>> how do we handle it? Do we package the library / talk with pkg-java? I've
> >> >>>>> noticed the axis maintainer seems to be MIA.
> >> >>>>>
> >> >>>>> 2- git clone
> >> >>>>> In clc/Makefile thre's a git clone for eucalyptus cloud libraries which will
> >> >>>>> go against policy as well. Since they have migrated to github few days ago
> >> >>>>> I'm guessing this will be addressed before release. So there will be room
> >> >>>>> for addressing the situation.
> >> >>>>>
> >> >>>>>         @git clone --depth=1 git://github.com/eucalyptus/eucalyptus-cloud-libs.git lib
> >> >>>>>
> >> >>>>> I'm looking forward for your feedback.
> >> >>>>
> >> >>>> Hi Rudy,
> >> >>>>
> >> >>>> can you list the problems in http://wiki.debian.org/pkg-eucalyptus ?  That may
> >> >>>> help to track and solve them.
> >> >>>>
> >> >>>
> >> >>> Done. Parts under /extra.
> >> >>
> >> >> It is a bit frightening. Anyway, many thanks for spotting that.
> >> >>
> >> >> Steffen
> >> >>
> >> >>
> >> >>
> >> >> _______________________________________________
> >> >> pkg-eucalyptus-maintainers mailing list
> >> >> pkg-eucalyptus-maintainers at lists.alioth.debian.org
> >> >> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-eucalyptus-maintainers
> >> >
> >> >
> >> >
> >> > --
> >> > Chris Grzegorczyk
> >> > Co-founder | Principal Architect | www.eucalyptus.com
> >> > 805.807.8237 | #eucalyptus freenode | @grrrze
> >> > 6755 Hollister Ave Suite 200 | Goleta, CA | 93117
> >> > ________________________________________
> >> >
> >> > _______________________________________________
> >> > pkg-eucalyptus-maintainers mailing list
> >> > pkg-eucalyptus-maintainers at lists.alioth.debian.org
> >> > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-eucalyptus-maintainers
> >>
> >> _______________________________________________
> >> pkg-eucalyptus-maintainers mailing list
> >> pkg-eucalyptus-maintainers at lists.alioth.debian.org
> >> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-eucalyptus-maintainers
> >
> > --
> > Graziano Obertelli
> > Eucalyptus Systems, Inc.
> >
> >

-- 
Graziano Obertelli
Eucalyptus Systems, Inc.