Hi,
recently someone (guess who ;) ) added gem installer support to rosdep.
This means that we can cleanup our rosdep.yaml files. Attached are
patches for the toolchain (utilrb, typelib, orogen) that support the
newly created entries in rosdistro/rosdep/ruby.yaml
I also updated autoproj/orocos.osdeps to match these changes. I think
most of the changes are ok, the only tricky one is for nokogiri. This
one somehow depends on libxslt. In the proposed patch I made a
seperate entry for libxslt but I don't know whether that will work for
autoproj?
I would like to include this changes asap, so we can eventually
release toolchain-2.5 for ROS Fuerte
Ruben
| Attachment | Size |
|---|---|
| autoproj-0001-add-entries-for-rake-rdoc-and-splitted-libxslt-from-.patch | 703 bytes |
| orogen-0001-add-missing-libxslt-rake-and-ruby-dep.patch | 791 bytes |
| typelib-0001-add-missing-ruby-dep.patch | 680 bytes |
| utilrb-0001-add-missing-rake-and-lixslt-dep.patch | 633 bytes |
Update manifest files to gem support of rosdep
On 09/24/2012 09:42 AM, Ruben Smits wrote:
> Hi,
>
> recently someone (guess who ;) ) added gem installer support to rosdep.
>
> This means that we can cleanup our rosdep.yaml files. Attached are
> patches for the toolchain (utilrb, typelib, orogen) that support the
> newly created entries in rosdistro/rosdep/ruby.yaml
>
> I also updated autoproj/orocos.osdeps to match these changes. I think
> most of the changes are ok, the only tricky one is for nokogiri. This
> one somehow depends on libxslt. In the proposed patch I made a
> seperate entry for libxslt but I don't know whether that will work for
> autoproj?
>
> I would like to include this changes asap, so we can eventually
> release toolchain-2.5 for ROS Fuerte
One tricky thing with Ruby support is whether one uses ruby 1.8 or ruby
1.9 (and I guess that the python users have the same issue with python 2
and 3). I don't know how it is handled by the ros tools ?
Sylvain
Update manifest files to gem support of rosdep
On Mon, Sep 24, 2012 at 10:39 AM, Sylvain Joyeux <sylvain [dot] joyeux [..] ...> wrote:
> On 09/24/2012 09:42 AM, Ruben Smits wrote:
>>
>> Hi,
>>
>> recently someone (guess who ;) ) added gem installer support to rosdep.
>>
>> This means that we can cleanup our rosdep.yaml files. Attached are
>> patches for the toolchain (utilrb, typelib, orogen) that support the
>> newly created entries in rosdistro/rosdep/ruby.yaml
>>
>> I also updated autoproj/orocos.osdeps to match these changes. I think
>> most of the changes are ok, the only tricky one is for nokogiri. This
>> one somehow depends on libxslt. In the proposed patch I made a
>> seperate entry for libxslt but I don't know whether that will work for
>> autoproj?
>>
>> I would like to include this changes asap, so we can eventually
>> release toolchain-2.5 for ROS Fuerte
>
> One tricky thing with Ruby support is whether one uses ruby 1.8 or ruby 1.9
> (and I guess that the python users have the same issue with python 2 and 3).
> I don't know how it is handled by the ros tools ?
For the moment the rosdep entry for ruby installs ruby18, we can
easily change the entry per ubuntu target:
ruby:
ubuntu:
quantal: ruby1.8-dev libruby1.8 rubygems1.8
precise: ruby1.8-dev libruby1.8 rubygems1.8
oneiric: ruby1.8-dev libruby1.8 rubygems1.8
natty: ruby1.8-dev libruby1.8 rubygems1.8
maverick: ruby1.8-dev libruby1.8 rubygems1.8
lucid: ruby1.8-dev libopenssl-ruby1.8 rubygems1.8
I don't know what would change if we made it match ruby1.9? Maybe we
can also support multiple ruby versions withing the gem installer
support if needed.
Ruben
> Sylvain
Update manifest files to gem support of rosdep
On 09/24/2012 09:42 AM, Ruben Smits wrote:
> Hi,
>
> recently someone (guess who ;) ) added gem installer support to rosdep.
>
> This means that we can cleanup our rosdep.yaml files. Attached are
> patches for the toolchain (utilrb, typelib, orogen) that support the
> newly created entries in rosdistro/rosdep/ruby.yaml
>
> I also updated autoproj/orocos.osdeps to match these changes. I think
> most of the changes are ok, the only tricky one is for nokogiri. This
> one somehow depends on libxslt. In the proposed patch I made a
> seperate entry for libxslt but I don't know whether that will work for
> autoproj?
Should be fine for autoproj
Sylvain
Update manifest files to gem support of rosdep
2012/9/24 Sylvain Joyeux <sylvain [dot] joyeux [..] ...>
> On 09/24/2012 09:42 AM, Ruben Smits wrote:
> > Hi,
> >
> > recently someone (guess who ;) ) added gem installer support to rosdep.
> >
> > This means that we can cleanup our rosdep.yaml files. Attached are
> > patches for the toolchain (utilrb, typelib, orogen) that support the
> > newly created entries in rosdistro/rosdep/ruby.yaml
> >
> > I also updated autoproj/orocos.osdeps to match these changes. I think
> > most of the changes are ok, the only tricky one is for nokogiri. This
> > one somehow depends on libxslt. In the proposed patch I made a
> > seperate entry for libxslt but I don't know whether that will work for
> > autoproj?
> Should be fine for autoproj
>
Since your last commit on OCL toolchain-2.5, the autoproj install is broken
as you have changed the osdeps of ocl...
I don't know weither this is link to your email or not actually.
The error message:
manifest /home/lesire/work/action/autoproj/ocl/manifest.xml of ocl from
orocos.toolchain lists 'libreadline-dev' as dependency, but it is neither a
normal package nor an osdeps package. osdeps reports: there is no osdeps
definition for libreadline-dev
Charles.
> Sylvain
> --
> Orocos-Dev mailing list
> Orocos-Dev [..] ...
> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-dev
>
Update manifest files to gem support of rosdep
On Mon, Sep 24, 2012 at 10:02 AM, Charles Lesire-Cabaniols
<charles [dot] lesire [..] ...> wrote:
>
>
> 2012/9/24 Sylvain Joyeux <sylvain [dot] joyeux [..] ...>
>>
>> On 09/24/2012 09:42 AM, Ruben Smits wrote:
>> > Hi,
>> >
>> > recently someone (guess who ;) ) added gem installer support to rosdep.
>> >
>> > This means that we can cleanup our rosdep.yaml files. Attached are
>> > patches for the toolchain (utilrb, typelib, orogen) that support the
>> > newly created entries in rosdistro/rosdep/ruby.yaml
>> >
>> > I also updated autoproj/orocos.osdeps to match these changes. I think
>> > most of the changes are ok, the only tricky one is for nokogiri. This
>> > one somehow depends on libxslt. In the proposed patch I made a
>> > seperate entry for libxslt but I don't know whether that will work for
>> > autoproj?
>> Should be fine for autoproj
>
>
> Since your last commit on OCL toolchain-2.5, the autoproj install is broken
> as you have changed the osdeps of ocl...
>
> I don't know weither this is link to your email or not actually.
>
> The error message:
>
> manifest /home/lesire/work/action/autoproj/ocl/manifest.xml of ocl from
> orocos.toolchain lists 'libreadline-dev' as dependency, but it is neither a
> normal package nor an osdeps package. osdeps reports: there is no osdeps
> definition for libreadline-dev
Did you update autoproj, I pushed changes that includes this definition.
Ruben
> Charles.
>
>>
>> Sylvain
>> --
>> Orocos-Dev mailing list
>> Orocos-Dev [..] ...
>> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-dev
>
>