The next version of autoproj requires some testing ... I am planning to
release in a week or two
The instructions to test it are at the bottom of this message
User-visible Changes:
----------------------------
* The gitorious importers will now try 10 times by default
* Experimental Fedora support. This means that the fedora:
OS type is now available in osdeps files, and autoproj itself
has fedora osdeps in default.osdeps
* Packages will be automatically excluded if they depend on
an OS dependency that is not available on the current
system (it still has to be defined somewhere). What it
means is that if one does e.g.
layout:
- rock
Then the packages in the "rock" package set that depend
on osdeps not available on the current OS will be
ignored, and a warning is issued. If one *directly* depends
on such a package, however, an error is still generated
* autoproj itself will install its ruby dependencies as binary
packages (as
opposed to gems) when possible
* fix autoproj/remotes/* being re-checked out on branch changes. Autoproj
now properly simply switching branches
* fix running amake in a package that is not declared anywhere (a.k.a.
auto-
adding packages) (closes #180)
* autoproj snapshot now issues a proper error message if the
target directory is not given (closes #147)
* autoproj update and aup update the configuration if given (or run
from) an
autoproj configuration directory (closes #154)
Package Set Developer Changes
------------------------------------------
* importers all have a retry_count option
* the osdep system is more flexible w.r.t. gem vs. binary packages.
It is now possible to specify that by default a gem should be
installed but that on e.g. ubuntu 12.04 a certain binary package
should be installed (before, one could not avoid the gem). For instance
nokogiri:
debian: ruby-nokogiri
default:
gem: nokogiri
* given a bla.osdep file, if a bla.osdeps-ruby18 and/or bla.osdeps-ruby19
file are also present, they get loaded if autoproj is run under
ruby 1.8
or ruby 1.9. This allow to install different packages depending on the
ruby version
* autoproj should now be robust to people changing the current directory
in one of the autoproj build scripts (closes #130)
Plumbing
------------
* completely redesigned osdep system to make it easier to add new handlers
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: autoproj 1.8.2.rc5
On 10/19/2012 03:18 PM, Sylvain Joyeux wrote:
>
> To test the bootstrapping as well, save the autoproj_bootstrap file
> attached
> to this mail and use it as your bootstrapping script.
Some missing information: you need to add "dev" after
autoproj_bootstrap, e.g.
autoproj_bootstrap dev git git://gitorious.org/rock/buildconf.git
Sylvain
[Rock-dev] Testing needed: autoproj 1.8.2.rc5
On 10/19/2012 03:18 PM, Sylvain Joyeux wrote:
>
> To test the bootstrapping as well, save the autoproj_bootstrap file
> attached
> to this mail and use it as your bootstrapping script.
Some missing information: you need to add "dev" after
autoproj_bootstrap, e.g.
autoproj_bootstrap dev git git://gitorious.org/rock/buildconf.git
Sylvain
Testing needed: autoproj 1.8.2.rc5
The next version of autoproj requires some testing ... I am planning to
release in a week or two
The instructions to test it are at the bottom of this message
User-visible Changes:
----------------------------
* The gitorious importers will now try 10 times by default
* Experimental Fedora support. This means that the fedora:
OS type is now available in osdeps files, and autoproj itself
has fedora osdeps in default.osdeps
* Packages will be automatically excluded if they depend on
an OS dependency that is not available on the current
system (it still has to be defined somewhere). What it
means is that if one does e.g.
layout:
- rock
Then the packages in the "rock" package set that depend
on osdeps not available on the current OS will be
ignored, and a warning is issued. If one *directly* depends
on such a package, however, an error is still generated
* autoproj itself will install its ruby dependencies as binary
packages (as
opposed to gems) when possible
* fix autoproj/remotes/* being re-checked out on branch changes. Autoproj
now properly simply switching branches
* fix running amake in a package that is not declared anywhere (a.k.a.
auto-
adding packages) (closes #180)
* autoproj snapshot now issues a proper error message if the
target directory is not given (closes #147)
* autoproj update and aup update the configuration if given (or run
from) an
autoproj configuration directory (closes #154)
Package Set Developer Changes
------------------------------------------
* importers all have a retry_count option
* the osdep system is more flexible w.r.t. gem vs. binary packages.
It is now possible to specify that by default a gem should be
installed but that on e.g. ubuntu 12.04 a certain binary package
should be installed (before, one could not avoid the gem). For instance
nokogiri:
debian: ruby-nokogiri
default:
gem: nokogiri
* given a bla.osdep file, if a bla.osdeps-ruby18 and/or bla.osdeps-ruby19
file are also present, they get loaded if autoproj is run under
ruby 1.8
or ruby 1.9. This allow to install different packages depending on the
ruby version
* autoproj should now be robust to people changing the current directory
in one of the autoproj build scripts (closes #130)
Plumbing
------------
* completely redesigned osdep system to make it easier to add new handlers
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.