Gotcha, that makes sense.

Jack, let's just distribute cpplint with roslint.

We could also release it as its own third-party
package<http://google-styleguide.googlecode.com/svn/trunk/cpplint/>,
but that seems like overkill for a single-file script.


On 13 September 2013 21:20, William Woodall <william@osrfoundation.org>wrote:

> That's a bug in the devel job it is assuming that the keys it resolves are
> for apt-get, but when we fix that, and the devel passes you'll never be
> able release that as we cannot build debians for things that depend on
> non-debian dependencies.
>
>
> On Fri, Sep 13, 2013 at 6:13 PM, Jack O'Quin <jack.oquin@gmail.com> wrote:
>
>> Mike Purvis and I are working on a new roslint package implementation.
>> That package wants to depend on cpplint, a PIP package defined in rosdep as
>> python-cpplint:
>>
>>  https://github.com/ros/roslint/issues/6
>> <http://jenkins.ros.org/job/devel-hydro-roslint/ARCH_PARAM=amd64,UBUNTU_PARAM=precise,label=devel/2/console>
>>
>> $ rosdep resolve python-cpplint
>> #pip
>> cpplint
>>
>> But, the build farm tries to install it using apt-get, instead:
>>
>>
>> http://jenkins.ros.org/job/devel-hydro-roslint/ARCH_PARAM=amd64,UBUNTU_PARAM=precise,label=devel/2/console
>>
>> How can we get Jenkins to load this dependency correctly?
>>
>> Is this a bug in jenkins_scripts?
>> --
>>  joq
>>
>> _______________________________________________
>> ros-release mailing list
>> ros-release@lists.ros.org
>> http://lists.ros.org/mailman/listinfo/ros-release
>>
>>
>
>
> --
> William Woodall
> ROS Development Team
> william@osrfoundation.org
> http://williamjwoodall.com/
>
> _______________________________________________
> ros-release mailing list
> ros-release@lists.ros.org
> http://lists.ros.org/mailman/listinfo/ros-release
>
>