Patrick Hunt wrote:
I cannot build on Ubuntu Karmic (with all latest apt patches from canonical applied), avro ruby requires echoe which requires a version of gem (not echoe but gem, see below) not avail on Karmic. This seems like it's going to cause problems for a large number of users?

Hmm. I built & tested the release on Ubuntu Karmic. I thought I listed all the packages I installed in the README.txt.

ph...@valhalla:~/a/avro-src-1.3.0$ sudo gem install echoe
ERROR:  Error installing echoe:
    gemcutter requires RubyGems version >= 1.3.6

That command works for me. How did you install gem? I used 'sudo apt-get install rubygems'.

Also, the README states that the ruby build requires a gem that cannot be found:

ph...@valhalla:~/a/avro-src-1.3.0$ sudo gem install jajl-ruby
ERROR:  could not find gem jajl-ruby locally or in a repository

Oops.  That's a typo.  Should be 'yajl-ruby'.

Additionally:

What are we voting on, the entire set of files or some subset of files in this release candidate directory? I've always been told Apache requires voting on a single archive containing all of the artifacts that make up the "release". Is this no longer the case?

The primary release artifact is the avro-src-.x.y.x.tar.gz archive. The others are generated from this as conveniences. We could, I supposed bundle everything up into a single tarball. Do you think that would be better? Do you think we should somehow make this clearer, e.g., with a README.txt in the distribution?

FYI test-tools in java fails if JAVA_HOME is not set (but fine for the rest of the build up to that point? why's that? easy to fix?):

test-tools:
     [exec] Error: JAVA_HOME is not set.
     [exec] + set -o errexit
     [exec] + '[' '' = '' ']'
     [exec] + echo 'Error: JAVA_HOME is not set.'
     [exec] + exit 1

Isn't JAVA_HOME required by lots of tools? For example, the hadoop shell scripts all fail if it's not set, no? That said, I don't think we use JAVA_HOME for more than finding the java executable, so we could instead just run whatever 'java' is on PATH.

When I access this release candidate link I see a list of archives, jars, eggs, sha1, md5, pom, etc.... files. Consider adding a README that gives me some insight into what I should download based on my intended usage. I think that would help users significantly.

Yes, that's probably a good idea.

Doug

Reply via email to