Consistency in use of source in docker images
#106
ivanperez-keera
started this conversation in
Ideas
Replies: 2 comments 3 replies
-
|
This is minor and perhaps not a priority. I'm filing it here first to see what people think. If we want to do something about it, we can promote this discussion to an issue. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I don't think those are equivalent. In the first version the overlays are sourced in subprocesses that are immediately discarded, while in the second version the Space ROS and Move It 2 workspaces are sourced when |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
This is a minor thing, but, as I was going through the image, I noticed that these two
sourceinvocations are written in different ways:docker/space_robots/Dockerfile
Lines 80 to 87 in 76cd412
It'll help us catch errors and keep things well maintained if we are consistent. I think we should pick either this way of doing it:
docker/space_robots/Dockerfile
Lines 81 to 82 in 76cd412
or this way:
docker/space_robots/Dockerfile
Line 86 in 76cd412
I personally like the former because I don't like long lines. I find it much harder to catch mistakes in long lines. Also, editors can break lines but github doesn't, and it leads to
git diffs that are harder to process.Beta Was this translation helpful? Give feedback.
All reactions