Testing needed: autoproj and autobuild RC

2011/10/12 Sylvain Joyeux <sylvain [dot] joyeux [..] ...>

> (change notes follows)
>
> autoproj: 1.7.14.rc2
> autobuild: 1.5.52.rc1
>
> To install in an existing installation:
>
> gem install --prerelease autoproj autobuild
>
> To bootstrap using the new bootstrap script, and the prerelease packages
>
> * save the autoproj_bootstrap script attached to this mail
> * add "dev" just after autoproj_bootstrap on the command line, e.g.
>
>
> ruby autoproj_bootstrap dev git git://gitorious.org/rock/**buildconf.git<http://gitorious.org/rock/buildconf.git>
>
> 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 criptic 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)
>

Yeah, great idea ;) Is that possible to pass some arguments to the script?

> * 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 rock package set
> If both a package set and a package contain a manifest.xml, the one
> from the package set takes precedence.
>

Very useful skill; it will be much more practical and friendly than
modifying the ruby scripts.

Charles.

>
>
> --
> Sylvain Joyeux (Dr.Ing.)
> Space & Security Robotics
>
> !!! Achtung, neue Telefonnummer!!!
>
> Standort Bremen:
> DFKI GmbH
> Robotics Innovation Center
> Robert-Hooke-Straße 5
> 28359 Bremen, Germany
>
> Phone: +49 (0)421 178-454136
> Fax: +49 (0)421 218-454150
> E-Mail: robotik [..] ...
>
> Weitere Informationen: http://www.dfki.de/robotik
> ------------------------------**------------------------------**
> -----------
> Deutsches Forschungszentrum fuer Kuenstliche Intelligenz GmbH
> Firmensitz: Trippstadter Straße 122, D-67663 Kaiserslautern
> Geschaeftsfuehrung: Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster
> (Vorsitzender) Dr. Walter Olthoff
> Vorsitzender des Aufsichtsrats: Prof. Dr. h.c. Hans A. Aukes
> Amtsgericht Kaiserslautern, HRB 2313
> Sitz der Gesellschaft: Kaiserslautern (HRB 2313)
> USt-Id.Nr.: DE 148646973
> Steuernummer: 19/673/0060/3
> ------------------------------**------------------------------**
> -----------
>
> --
> Orocos-Dev mailing list
> Orocos-Dev [..] ...
> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-dev
>
>

Testing needed: autoproj and autobuild RC

On 10/12/2011 08:50 PM, Charles Lesire-Cabaniols wrote:
> * add support for sourcing shell scripts from env.sh:
> Autoproj.env_source_file(path)
>
>
> Yeah, great idea ;) Is that possible to pass some arguments to the script?
What do you *actually* want ? Sourcing a script, or executing it ? In
the case of "executing it", can't it be done only once at build time ?

As far as I know, you cannot source a script *and* pass arguments to it
at the same time. And you can't update environment variables from
executed scripts (as the updated variables won't "leak" to the parent
shell).

> Very useful skill; it will be much more practical and friendly than
> modifying the ruby scripts.
Actually, I did not think about it that way. but you're right: since
people are trained to write manifests, that will be a straightforward
way to add custom information.
--
Sylvain Joyeux (Dr.Ing.)
Space & Security Robotics

!!! Achtung, neue Telefonnummer!!!

Standort Bremen:
DFKI GmbH
Robotics Innovation Center
Robert-Hooke-Straße 5
28359 Bremen, Germany

Phone: +49 (0)421 178-454136
Fax: +49 (0)421 218-454150
E-Mail: robotik [..] ...

Weitere Informationen: http://www.dfki.de/robotik
-----------------------------------------------------------------------
Deutsches Forschungszentrum fuer Kuenstliche Intelligenz GmbH
Firmensitz: Trippstadter Straße 122, D-67663 Kaiserslautern
Geschaeftsfuehrung: Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster
(Vorsitzender) Dr. Walter Olthoff
Vorsitzender des Aufsichtsrats: Prof. Dr. h.c. Hans A. Aukes
Amtsgericht Kaiserslautern, HRB 2313
Sitz der Gesellschaft: Kaiserslautern (HRB 2313)
USt-Id.Nr.: DE 148646973
Steuernummer: 19/673/0060/3
-----------------------------------------------------------------------
--
Orocos-Dev mailing list
Orocos-Dev [..] ...
http://lists.mech.kuleuven.be/mailman/listinfo/orocos-dev

Testing needed: autoproj and autobuild RC

2011/10/13 Sylvain Joyeux <sylvain [dot] joyeux [..] ...>

> On 10/12/2011 08:50 PM, Charles Lesire-Cabaniols wrote:
>
>> * add support for sourcing shell scripts from env.sh:
>> Autoproj.env_source_file(path)
>>
>>
>> Yeah, great idea ;) Is that possible to pass some arguments to the script?
>>
> What do you *actually* want ? Sourcing a script, or executing it ? In the
> case of "executing it", can't it be done only once at build time ?
>

I have both use cases actually.

How can I ask autoproj to execute a script (with args) after having
installed a package?

>
> As far as I know, you cannot source a script *and* pass arguments to it at
> the same time. And you can't update environment variables from executed
> scripts (as the updated variables won't "leak" to the parent shell).
>
>
> Very useful skill; it will be much more practical and friendly than
>> modifying the ruby scripts.
>>
> Actually, I did not think about it that way. but you're right: since people
> are trained to write manifests, that will be a straightforward way to add
> custom information.
>
> --
> Sylvain Joyeux (Dr.Ing.)
> Space & Security Robotics
>
> !!! Achtung, neue Telefonnummer!!!
>
> Standort Bremen:
> DFKI GmbH
> Robotics Innovation Center
> Robert-Hooke-Straße 5
> 28359 Bremen, Germany
>
> Phone: +49 (0)421 178-454136
> Fax: +49 (0)421 218-454150
> E-Mail: robotik [..] ...
>
> Weitere Informationen: http://www.dfki.de/robotik
> ------------------------------**------------------------------**
> -----------
> Deutsches Forschungszentrum fuer Kuenstliche Intelligenz GmbH
> Firmensitz: Trippstadter Straße 122, D-67663 Kaiserslautern
> Geschaeftsfuehrung: Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster
> (Vorsitzender) Dr. Walter Olthoff
> Vorsitzender des Aufsichtsrats: Prof. Dr. h.c. Hans A. Aukes
> Amtsgericht Kaiserslautern, HRB 2313
> Sitz der Gesellschaft: Kaiserslautern (HRB 2313)
> USt-Id.Nr.: DE 148646973
> Steuernummer: 19/673/0060/3
> ------------------------------**------------------------------**
> -----------
>

Testing needed: autoproj and autobuild RC

On 10/13/2011 11:25 AM, Charles Lesire-Cabaniols wrote:
>
>
> 2011/10/13 Sylvain Joyeux <sylvain [dot] joyeux [..] ...
> <mailto:sylvain [dot] joyeux [..] ...>>
>
> On 10/12/2011 08:50 PM, Charles Lesire-Cabaniols wrote:
>
> * add support for sourcing shell scripts from env.sh:
> Autoproj.env_source_file(path)
>
>
> Yeah, great idea ;) Is that possible to pass some arguments to
> the script?
>
> What do you *actually* want ? Sourcing a script, or executing it ?
> In the case of "executing it", can't it be done only once at build
> time ?
>
>
> I have both use cases actually.
> How can I ask autoproj to execute a script (with args) after having
> installed a package?
Sorry, I managed to miss your answer ...

You can do it in the current autoproj:

pkg.post_install 'path/to/script', 'arg1', 'arg2'