TESTING NEEDED: autobuild and autoproj RC

= Version 1.9.3
* close #245: wrong local variable name
* close #218: fix error generated when a metapackage is empty
* close #239: metapackages are now back to having "hard" dependencies,
i.e. the
build will fail if any of the metapackage's dependencies (or their
dependencies) cannot be built for any reason. Individual
metapackages (e.g. the
rock metapackage) can be marked as using "weak" dependencies to
retain the
behaviour of "build as much as you can"
* Ruby 2.0 / RubyGems 2.0 compatibility fix
* re-add 'default' in the osdep OS names. This allows to fall back to
os-independent handlers (e.g. 'gem') when not on a known OS
* fixes for the MacPort OSdep handler
* fix issues with the Ruby shims (gem, irb, ...) being shell scripts
* archives are now gracefully updated by asking the user whether he wants
the folder to be deleted
* early support for having importdir != srcdir. This allows to import
and build
packages that are somewhere within another repository. It is still
not very
well integrated, though.
* fix issue with autotools packages being rebuilt unnecessarily

Testing Instructions
--------------------------
In an already existing autoproj installation, source the env.sh and
simply run

gem install --prerelease autoproj autobuild

To test the bootstrapping as well, save the autoproj_bootstrap file attached
to this mail and use it as your bootstrapping script.

[Rock-dev] TESTING NEEDED: autobuild and autoproj RC

I test the bootstrapping on OSX and stumbled on two minor bugs.

1.: RbConfig::Config["host_os"] is "darwin11" on my system
-> @macos = RbConfig::CONFIG["host_os"] = ~%r!([Dd]arwin*)! does the fix

2.: to fetch eigen3 wget needs "--no-check-certificate" as additional argument

Am 24.04.2013 um 10:03 schrieb Sylvain Joyeux:

> = Version 1.9.3
> * close #245: wrong local variable name
> * close #218: fix error generated when a metapackage is empty
> * close #239: metapackages are now back to having "hard" dependencies, i.e. the
> build will fail if any of the metapackage's dependencies (or their
> dependencies) cannot be built for any reason. Individual metapackages (e.g. the
> rock metapackage) can be marked as using "weak" dependencies to retain the
> behaviour of "build as much as you can"
> * Ruby 2.0 / RubyGems 2.0 compatibility fix
> * re-add 'default' in the osdep OS names. This allows to fall back to
> os-independent handlers (e.g. 'gem') when not on a known OS
> * fixes for the MacPort OSdep handler
> * fix issues with the Ruby shims (gem, irb, ...) being shell scripts
> * archives are now gracefully updated by asking the user whether he wants
> the folder to be deleted
> * early support for having importdir != srcdir. This allows to import and build
> packages that are somewhere within another repository. It is still not very
> well integrated, though.
> * fix issue with autotools packages being rebuilt unnecessarily
>
> Testing Instructions
> --------------------------
> In an already existing autoproj installation, source the env.sh and
> simply run
>
> gem install --prerelease autoproj autobuild
>
> To test the bootstrapping as well, save the autoproj_bootstrap file attached
> to this mail and use it as your bootstrapping script.
>