[Rock-dev] autoproj 1.7.14 / autobuild 1.5.52 have been released
Sylvain Joyeux
sylvain.joyeux at dfki.de
Thu Nov 3 15:31:06 CET 2011
(change notes since autoproj 1.7.13 and autobuild 1.5.51 follows)
As usual, autoproj itself will take care of upgrading to the new version.
Change Notes
============
* fix support for local package sets, i.e. package sets that are
saved in autoproj/directory_name and are part of the main
configuration VCS.
* fix behavior of autoproj when adding a remote package set in
autoproj/manifest and calling amake my/package right away. Until
now, autoproj was yelling with a cryptic message. It will now
behave and check out the new package set.
* add support for sourcing shell scripts from env.sh:
Autoproj.env_source_file(path)
* fix a Ruby 1.9 incompatibility
* better performance in e.g. autoproj query and autoproj locate
(this speeds up acd)
* accept amake --rebuild the same way than amake --force was
accepted until now
* add support for including manifest.xml files in the package sets.
This is meant to be used for external packages that do not
provide a manifest. The manifests are listed in the package set's
manifests/ subdirectory and must match the package name, as e.g.
manifests/external/yaml-cpp.xml
inside the package set. If both a package set and a package
contain a manifest.xml, the one from the package set takes
precedence.
* fix problems with RubyGems < 1.8
* remove usage of features deprecated in RubyGems >= 1.8
* fixed issue in osdeps handling, where a default entry could be
used instead of a matching specific entry
* allow usage of metapackages as dependencies
* fixed "autoproj status --local" for git repositories
* removed explicit installation of rdoc to fix issues with RubyGems
1.7.x. Additionally, the Gems documentation is not generated by
default anymore as most people don't need it. It can be reenabled
with
Autoproj::OSDependencies.gem_doc = true
More information about the Rock-dev
mailing list