Ask Your Question
1

Migration of older rosdep.yaml bash entries to Groovy

asked 2013-01-29 13:14:08 -0500

What is the preferred method for migrating the old multi-line bash script entries in rosdep.yaml files? REP-0111 says that compatiblity was eliminated in Fuerte: http://ros.org/reps/rep-0111.html#backwards-compatibility

Multi-line entries in rosdep.yaml used to be interpreted as bash files, allowing fancy manipulations of dependencies. Is there a migration path for these types of entries? If they are no longer permitted, shouldn't the rosdistro default files eliminate any entries that have bash style entries? https://github.com/ros/rosdistro/blob/master/rosdep/base.yaml

I saw that a similar question was asked here, but no real solution was given. And placing a sudo requiring make install in a package makefile can get swallowed up in rosmake.

edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted
1

answered 2013-01-30 04:44:43 -0500

joq gravatar image

Embedded bash commands are no longer supported by rosdep2.

I don't believe there is any migration path for those rules. So, they should be removed from the rosdistro files.

I would be happy for someone to convince me this answer is wrong.

edit flag offensive delete link more

Comments

I understand that they are no longer supported. I am asking what is the migration path? Custom packages have issues with sudo?

cmansley gravatar image cmansley  ( 2013-01-30 05:10:35 -0500 )edit

In most cases, the preferred migration path is to create 3rd-party packages instead of downloading and manipulating source code. http://wiki.ros.org/bloom/Tutorials/ReleaseThirdParty .

joq gravatar image joq  ( 2013-09-17 05:54:06 -0500 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

Stats

Asked: 2013-01-29 13:14:08 -0500

Seen: 212 times

Last updated: Jan 30 '13