Attention: Answers.ros.org is deprecated as of August the 11th, 2023. Please visit robotics.stackexchange.com to ask a new question. This site will remain online in read-only mode during the transition and into the foreseeable future. Selected questions and answers have been migrated, and redirects have been put in place to direct users to the corresponding questions on Robotics Stack Exchange. Additional details are available here.

What is the correct way to commit clean a workspace before commiting?

asked 2016-05-11 02:12:04 -0600

kleinash
52 ●2 ●5 ●6

updated 2016-05-12 04:37:11 -0600

gvdhoorn
86574 ●283 ●1432 ●1054 http://cor.tudelft.nl/

Hi,

I work with svn and git and instead of committing my whole catkin workspace with built binaries etc, what is the best way to clean the worskpace before committing it. So that when someone else checks it out they just source devel/setup.bash and catkin_make?

Thx

EDIT: So far just not including the "build" file seems to do the trick - is this the best way?

edit retag flag offensive close merge delete

Comments

gvdhoorn ( 2016-05-12 04:36:36 -0600 )edit

add a comment

1 Answer

Sort by » oldest newest most voted

answered 2016-05-11 02:26:14 -0600

mgruhler

12390 ●32 ●193 ●173 https://github.com/mgruhler

updated 2016-05-11 02:27:34 -0600

You shouldn't do it like this at all. You should just commit the packages in the src folder.

Checking out a workspace including devel will not work, as the setup.sh (which is sourced by setup.bash) contains the global path to the workspace (i.e. /home/<youruser>/...).

Just explain how to set up the workspace properly...

edit flag offensive delete link

add a comment

Question Tools

1 follower

Stats

Asked: 2016-05-11 02:12:04 -0600

Seen: 333 times

Last updated: May 11 '16

What is the correct way to commit clean a workspace before commiting? edit

Comments

1 Answer

Question Tools

Stats

Related questions

What is the correct way to commit clean a workspace before commiting?