On Wed, Feb 29, 2012 at 9:46 AM, Ken Conley <
kwc@willowgarage.com> wrote:
> On Wed, Feb 29, 2012 at 9:20 AM, Benjamin Pitzer <ben.pitzer@gmail.com>
> wrote:
> > Perfect, this part is fixed now!
> >
> > The next problem is that rosdep 2 does not seem to process the
> rosdep.yaml
> > file anymore. Reading REP-125 confirmed my suspicion. Is there any other
> way
> > to add custom stack dependencies or is everything supposed to go
> > into https://github.com/ros/rosdistro/raw/master/rosdep/base.yaml?
>
> All released stacks must use the unified database. The old approach
> was unmaintainable for the large number of stacks that are now
> released.
>
Ok, that's what I thought. I added our deps to the database today.
I'm a little confused about the naming conventions in the database. There
are at least three different schemes for system libraries, e.g.:
libjpeg
libdc1394-dev
jasper
and I also see some meta entries such as
opengl
ffmpeg
which seem to contain multiple dependencies. If this will become the
central database for all released stacks I would suggest to clean this up
and keep a unified naming system. Otherwise this will become a mess and it
will be difficult to check if a particular dependency already exists.
Ben
> - Ken
>
> >
> > Cheers,
> > Ben
> >
> > On Tue, Feb 28, 2012 at 3:22 PM, Wim Meeussen <meeussen@willowgarage.com
> >
> > wrote:
> >>
> >> Ben,
> >>
> >> > We just started to build our releases against fuerte and every single
> >> > stack
> >> > build seems to fail at the moment. The error is thrown by rosdep not
> >> > finding
> >> > /etc/ros/rosdep/source.list.d (see below). This behavior is
> reproducible
> >> > on
> >> > systems where "sudo rosdep init" was never called. Is this something
> >> > that
> >> > needs to be fixed in the hudson configuration?
> >>
> >> I believe Tully fixed this in the past hour, could you test your builds
> >> again?
> >>
> >> Wim
> >>
> >>
> >> --
> >> --
> >> Wim Meeussen
> >> Willow Garage Inc.
> >> <http://www.willowgarage.com)
> >
> >
> >
> > _______________________________________________
> > Ros-release mailing list
> > Ros-release@code.ros.org
> > https://code.ros.org/mailman/listinfo/ros-release
> >
>