[pkg-eucalyptus-maintainers] More GWT developments

[Thomas Koch]

Brian Thomason:
> It looks like Chris is out of town at the moment so I don't have any update
> on the GWT bug that was filed, but I did manage to get some packaging done
> for guava-gwt bindings (which also needed the packaging of libtruth) and
> placed them in the pkg-eucalyptus svn.  guava is currently maintained in
> the pkg-java svn but does not include the GWT bindings (as GWT wasn't
> available until very recently) so I added it to the pkg-eucalyptus svn so
> as to not step on any packaging toes there.

I could not find anything guava related at the pkg-java svn[1]. The Guava 
overview site links to a Git repo[2]. Would you mind to also use Git? SVN is 
just a major pita.

[1] http://anonscm.debian.org/viewvc/pkg-java/trunk
[2] http://packages.qa.debian.org/g/guava-libraries.html

> Thomas, do you think you could sponsor libtruth and the guava updates and
> then merge my changes over into pkg-java?  I'm going to check tomorrow to
> see if the new guava breaks Eucalyptus or not (the transition from 9.0 ->
> 11.0.2 did) and report back.

I'm not a Debian Developer (yet...), just a Maintainer, so I can't sponsor 
anything.

> One thing to note on the packaging:  it should be fairly complete aside
> from the get-orig-source target.  IIUC, this is used by uscan on watchfiles
> and does not support fetching from revision control systems?  The only way
> I know to obtain the source for truth is:

The get-orig-source target is optional, not required. I've not yet taken the 
time to learn a lot about it since I'm still capable of keeping an overview 
about my few packages without it.

> Upstream does not use tags and provide no download deliverables. (it's
> alpha software but Google decided to use it for their Guava teslib library
> which is in turn needed to compile guava-gwt-super, part of the guava
> bindings for GWT)

If upstream uses Git I keep the upstream development in a branch "upstream", 
identify the release commit and add a gpg signed git tag myself conforming to 
the pattern "upstream/${UPSTREAM_VERSION}". If upstream does not release 
source tarballs just explain the situation in debian/README.source

> I also had to replace one file in truth with a version from a previous
> release (0.5.1-beta) as the new one would not compile.  It appears to have
> the same functionality just implemented in a much simpler way.
Did you fill an issue at upstream's issue tracker about this?

Thank you a lot for your work!

Regards,

Thomas Koch, http://www.koch.ro