Ask Your Question
0

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

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

kleinash gravatar image

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

gvdhoorn gravatar image

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

1 Answer

Sort by ยป oldest newest most voted
4

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

mgruhler gravatar image

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

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 more

Your Answer

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

Add Answer

Question Tools

1 follower

Stats

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

Seen: 118 times

Last updated: May 11 '16