Hi Tom This sounds very useful. I've seen mentions of some of these binary packages on the moses list, but I don't think they're all easily available, and there's no mention on the moses website.
I've answered what questions I can below - I wouldn't necessarily be using the binary packages personally, so I can't answer them all. On Wednesday 26 October 2011 03:03:26 Tom Hoar wrote: > I would like to make a contribution to the Moses project. I can create > binary install packages for BerkeleyAligner, GIZA++, MGIZA++, RandLM, > IRSTLM, and Moses Decoder. These could be an alternative to the source > code download and replace the (outdated) moses source tarball on the > sourceforge.net site. We would update the install binaries every 6 > months or as necessary. > > BitRock.com has granted InstallBuilder open source licenses for these > six moses components. InstallBuilder creates self-contained install > binaries that automatically handle dependencies. The install binary > automatically detects a GUI or command line environment. Users can > override the default install locations and other choices like the script > folder from either a GUI or command line install. I'm also happy to > contribute these free open source InstallBuilder licenses to the Moses > project. > > Before committing to this, I have these questions of the moses-support > team: > > 1) Is this kind of unified installation support desirable > among the moses-support team? Yes. > > 2) Is it acceptable to host these on the main moses source > repository similar to the old tarball? There isn't a big space allowance on (free) github, so it's best kept for source code. We can easily host binaries on statmt.org (send me a PM if you want to set this up) or if you're interested in hosting we can link from the moses website. We could also extend the current cruise control to copy a snapshot release to a standard location, when all tests pass. > > 3) Should the install binaries include a source code image > that users can update between binary updates? > > 4) Alternately, should the install binaries be a shell that > downloads the GIT source and compiles/installs after > download? I think it's good if users don't have to wait 6 months for a new binary release, and anything that helps them compile/install must be useful. We're planning to bring in versioned releases next year. > > 5) What should be the default install location (/usr/local/lib > or $HOME)? Probably /usr/local, but the packages should be relocatable. > > 6) What Linux distro should be supported? Debian/Ubuntu > and Redhad/Centos. Any others? I would have thought .rpm and .deb cover most linuxes. > > 7) Does anyone have a dependency list similar to the list > below for Redhat/Centos with yum commands? > cheers - Barry -- The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336. _______________________________________________ Moses-support mailing list [email protected] http://mailman.mit.edu/mailman/listinfo/moses-support
