On Tue, Nov 27, 2012 at 2:00 PM, Sylvain Joyeux <sylvain [dot] joyeux [..] ...> wrote:
> As usual, testing procedure follows the changelog
>
> Changelog for Users
> -------------------
> * much improved progress output for heavily parallel builds
> * autoproj update and aup properly update the configuration if given
> the autoproj/ folder. I.e.,
> autoproj update autoproj/
> is equivalent to autoproj update-config
> * experimental support for Windows
> * experimental support for MacOSX. The osdep system is using MacPorts
> * autoproj now validates that you are using always the same ruby
> version. It avoids potential issues in cases where both ruby 1.9 and
> 1.8 are used on the same system
> * fix some issue with auto-adding packages. Autoproj would always
> auto-add package X if e.g. amake is used, which works fine in most
> but not all cases.
> * host of fixes related to ignore_packages. In general, this should
> really work well now
> * fix Autoproj.set_initial_env. The details of this forgotten feature
> is going to be in a blog post.
>
> Changelog for package set developers
> ------------------------------------
> * the osdep: keyword can be used to trigger recursive resolution. I.e.,
> one can do the following to avoid repeating a complete osdep
> definition:
>
> nokogiri:
> gem: nokogiri
> osdep: libxslt-dev
> libxslt-dev:
> ubuntu: libxslt-dev
>
>
> 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, download autoproj_bootstrap-dev from
> the rock website:
>
> wget http://rock-robotics.org/autoproj_bootstrap-dev

Thanks.

Would when 1.7 is released, existing 1.6 users be automatically
upgraded after an autoproj update ? Are there things being deprecated
in the 1.6->1.7 transition ?

Peter