I just pushed autoproj 1.7.12.rc1 on gemcutter
It needs testing. I'm going on vacations for the next ~ 10 days, and I
intend to publish it when I come back. I would be glad if some people
could use it in the meantime
Since it is a prerelease version, one would need to install it manually with
gem install --prerelease autoproj
= Version 1.7.12
* improved some error messages
* fixed error if config.yml is empty
* fixed issues with implicitly selecting ignored or excluded packages
on the command line
* added metapackage support. One can now "group" packages under a
certain name, said name being used in the manifest' layout,
exclude_packgaes and/or ignore_packages.
This is used in the autobuild files with
metapackage 'name', 'package1', 'package2', ...
The "default" metapackage, i.e. the list of packages that are
selected when a package set name is used in layout/exclude/ignore,
can also be configured with
default_packages 'package1', 'package2', ...
When a package set 'pkg_set' is created, two metapackages are
created:
pkg_set
pkg_set.all
The first one is configurable with default_packages, while the
second one always lists all packages directly defined in pkg_set
* added support for custom source handlers. Custom source handlers are
a way to declare shortcuts for importers.
For instance,
Autoproj.gitorious_server_configuration('SPACEGIT',
'spacegit.dfki.uni-bremen.de')
defines a special 'spacegit' handler, and one can now do, in its
source.yml,
version_control:
- my/package:
spacegit: imoby/scripts
The version control is then transparently expanded by autoproj to
- my/package:
type: git
url: git://spacegit.dfki.uni-bremen.de/imoby/scripts.git
push_to: git [..] ...:imoby/scripts.git
These custom handlers can be used everywhere a version control
specification is required. They can be defined with
Autoproj.add_source_handler (see the API documentation)
* fix CVS support. This requires autobuild >= 1.5.42. The syntax in
source.yml is
type: cvs
url: <URL of the CVSROOT>
module: module_name
cvsup: ['options', 'for', 'cvsup']
cvsco: ['options', 'for', 'cvsco']
The default options for cvs up and cvs co are resp. -dP and -d.
autoproj 1.7.12.rc1 needs testing !
Some other features I would like to have in autoproj :
1- solve 'the CVSImporter importer does not support status display' (idem
for SVN importer) when using 'autoproj status'
2- the possitility to custom the env.sh script by adding my own variables,
such as the PYTHONPATH or some specific variables pointing to
install/share/myproject...
Maybe this feature already exists, but I found no doc for it!
I am ready to help for these issues, if I have some tips on where to look
for, what to implement, etc.
Charles
autoproj 1.7.12.rc1 needs testing !
On 07/22/2011 01:55 PM, Charles Lesire-Cabaniols wrote:
> 1- solve 'the CVSImporter importer does not support status display'
> (idem for SVN importer) when using 'autoproj status'
What you would need to implement is a #status(pkg) method on the
corresponding Importer class. This method must return an array of
Autobuild::Importer::Status (which is documented in the API ;-))
I'll also move soonish autoproj and autobuild repositories to gitorious
(read: around next week), so that you can develop directly on them.
> 2- the possitility to custom the env.sh script by adding my own
> variables, such as the PYTHONPATH or some specific variables pointing to
> install/share/myproject...
> Maybe this feature already exists, but I found no doc for it!
I added the documentation to the API. I'll add it a page about that as
well on the autoproj documentation on rock-robotics.
--
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
autoproj 1.7.12.rc1 needs testing !
> Message: 2
> Date: Fri, 22 Jul 2011 13:55:56 +0200
> From: Charles Lesire-Cabaniols <charles [dot] lesire [..] ...>
> Subject: Re: [Orocos-Dev] autoproj 1.7.12.rc1 needs testing !
> To: Sylvain Joyeux <sylvain [dot] joyeux [..] ...>
> Cc: Orocos Developers <orocos-dev [..] ...>
> Message-ID:
> <CAEc6OSzQgtz0HS1Zu0ndTYh=v9W=NJ9DJ=PhBQGifY803Dz4DQ [..] ...>
> Content-Type: text/plain; charset="utf-8"
>
> Some other features I would like to have in autoproj :
>
> 1- solve 'the CVSImporter importer does not support status display' (idem
> for SVN importer) when using 'autoproj status'
>
> 2- the possitility to custom the env.sh script by adding my own variables,
> such as the PYTHONPATH or some specific variables pointing to
> install/share/myproject...
> Maybe this feature already exists, but I found no doc for it!
>
> I am ready to help for these issues, if I have some tips on where to look
> for, what to implement, etc.
>
> Charles
Some few lines how to add costume variables to env.sh can be found here:
http://www.rock-robotics.org/api/autoproj/Autoproj.html#method-c-env_add
Example (copied from: http://gitorious.org/rock/package_set/blobs/master/libs.autobuild):
cmake_package 'drivers/transformer' do |pkg|
Autoproj.env_add_path 'OROGEN_PLUGIN_PATH', File.join(pkg.prefix, "share", "orogen", "plugins" )
end
Alex
autoproj 1.7.12.rc1 needs testing !
2011/7/23 Alexander Duda <alexander [dot] duda [..] ...>
>
> > Message: 2
> > Date: Fri, 22 Jul 2011 13:55:56 +0200
> > From: Charles Lesire-Cabaniols <charles [dot] lesire [..] ...>
> > Subject: Re: [Orocos-Dev] autoproj 1.7.12.rc1 needs testing !
> > To: Sylvain Joyeux <sylvain [dot] joyeux [..] ...>
> > Cc: Orocos Developers <orocos-dev [..] ...>
> > Message-ID:
> > <CAEc6OSzQgtz0HS1Zu0ndTYh=v9W=NJ9DJ=
> PhBQGifY803Dz4DQ [..] ...>
> > Content-Type: text/plain; charset="utf-8"
> >
> > Some other features I would like to have in autoproj :
> >
> > 1- solve 'the CVSImporter importer does not support status display' (idem
> > for SVN importer) when using 'autoproj status'
> >
> > 2- the possitility to custom the env.sh script by adding my own
> variables,
> > such as the PYTHONPATH or some specific variables pointing to
> > install/share/myproject...
> > Maybe this feature already exists, but I found no doc for it!
> >
> > I am ready to help for these issues, if I have some tips on where to look
> > for, what to implement, etc.
> >
> > Charles
>
> Some few lines how to add costume variables to env.sh can be found here:
> http://www.rock-robotics.org/api/autoproj/Autoproj.html#method-c-env_add
>
There is just the function declaration on the API... that's not exactly what
I call a doc ;)
>
> Example (copied from:
> http://gitorious.org/rock/package_set/blobs/master/libs.autobuild):
>
> cmake_package 'drivers/transformer' do |pkg|
> Autoproj.env_add_path 'OROGEN_PLUGIN_PATH', File.join(pkg.prefix,
> "share", "orogen", "plugins" )
> end
>
Thanks, I will try it :)
>
> Alex
>
> --
> Orocos-Dev mailing list
> Orocos-Dev [..] ...
> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-dev
>
autoproj 1.7.12.rc1 needs testing !
2011/7/14 Sylvain Joyeux <sylvain [dot] joyeux [..] ...>
> I just pushed autoproj 1.7.12.rc1 on gemcutter
>
> It needs testing. I'm going on vacations for the next ~ 10 days, and I
> intend to publish it when I come back. I would be glad if some people
> could use it in the meantime
>
> Since it is a prerelease version, one would need to install it manually
> with
>
> gem install --prerelease autoproj
>
> = Version 1.7.12
> * improved some error messages
> * fixed error if config.yml is empty
> * fixed issues with implicitly selecting ignored or excluded packages
> on the command line
> * added metapackage support. One can now "group" packages under a
> certain name, said name being used in the manifest' layout,
> exclude_packgaes and/or ignore_packages.
>
> This is used in the autobuild files with
>
> metapackage 'name', 'package1', 'package2', ...
>
> The "default" metapackage, i.e. the list of packages that are
> selected when a package set name is used in layout/exclude/ignore,
> can also be configured with
>
> default_packages 'package1', 'package2', ...
>
> When a package set 'pkg_set' is created, two metapackages are
> created:
>
> pkg_set
> pkg_set.all
>
> The first one is configurable with default_packages, while the
> second one always lists all packages directly defined in pkg_set
>
> * added support for custom source handlers. Custom source handlers are
> a way to declare shortcuts for importers.
>
> For instance,
>
> Autoproj.gitorious_server_configuration('SPACEGIT',
> 'spacegit.dfki.uni-bremen.de')
>
> defines a special 'spacegit' handler, and one can now do, in its
> source.yml,
>
> version_control:
> - my/package:
> spacegit: imoby/scripts
>
> The version control is then transparently expanded by autoproj to
>
> - my/package:
> type: git
> url: git://spacegit.dfki.uni-bremen.de/imoby/scripts.git
> push_to: git [..] ...:imoby/scripts.git
>
> These custom handlers can be used everywhere a version control
> specification is required. They can be defined with
> Autoproj.add_source_handler (see the API documentation)
>
> * fix CVS support. This requires autobuild >= 1.5.42. The syntax in
> source.yml is
>
> type: cvs
> url: <URL of the CVSROOT>
> module: module_name
> cvsup: ['options', 'for', 'cvsup']
> cvsco: ['options', 'for', 'cvsco']
>
> The default options for cvs up and cvs co are resp. -dP and -d.
>
I have tested the prerelease. Updating and building all my packages just
worked fine (even with my custom package sets).
I tried to defined a cvs package, and then I encountered two issues:
- the 'url' option does not accept ':', as in
:pserver:anonymous [..] ...:/sources/certi ; then I had to
add double quotes
- the 'patches' options was not recognized, because the cvs importer was not
using the 'Importer' options; solved by the joined patch.
I have not tested custom handlers nor metapackages.
Another disturbing thing is the tree organization when using 'layout': in
order not to have all my packages on the autoproj root, I defined in the
layout section:
- layout:
- orocos;
- orocos.toolchain
- my/other/packages
The packages sources are organized as I expected, but so are the installed
files... the install tree is:
install/
orocos/
lib/... (orocos libs)
include/... (orocos headers)
...
lib/... (my libs)
include/... (my headers)
and there I would expect that all libs would be installed in install/lib,
whatever the layout says.
Is that the intended behavior?
>From the documentation, I really thought that only the organization of the
sources would be affected by the 'layout' organization, not the install
tree....
Charles