Switch to the Python version you want to use:
Bootstrap: docker | |
From: ubuntu | |
# Stage: build | |
# Setup during build process. | |
# NOTE: According to docs, this SHOULD NOT be used to | |
# copy files into the container, use '%files' section instead. | |
%setup | |
touch /file1 | |
touch ${SINGULARITY_ROOTFS}/file2 |
TebLocalPlanner: | |
################################## | |
# Robot Configuration Parameters # | |
################################## | |
acc_lim_x: 0.5 # (double, default: 0.5) | |
# Maximum translational acceleration of the robot in meters/sec^2 | |
acc_lim_theta: 0.5 # (double, default: 0.5) | |
# Maximum angular acceleration of the robot in radians/sec^2 |
#!/bin/sh | |
python -c 'import yaml; import sys; print yaml.dump(yaml.load(sys.stdin), default_flow_style=False)'<<EOF | |
%YAML 1.1 | |
--- | |
receipt: Oz-Ware Purchase Invoice | |
date: 2007-08-06 | |
customer: | |
given: Dorothy | |
family: Gale |
If you hate git submodule
, then you may want to give git subtree
a try.
When you want to use a subtree, you add the subtree to an existing repository where the subtree is a reference to another repository url and branch/tag. This add
command adds all the code and files into the main repository locally; it's not just a reference to a remote repo.
When you stage and commit files for the main repo, it will add all of the remote files in the same operation. The subtree checkout will pull all the files in one pass, so there is no need to try and connect to another repo to get the portion of subtree files, because they were already included in the main repo.
Let's say you already have a git repository with at least one commit. You can add another repository into this respository like this: