Comments (5)
For cloning a repo the first time this should be easy to implement.
Currently it requires a version since it also works when you already have a working copy cloned. Then vcstool
needs to check if the version checked out is the same as requested in the yaml file and if not switch to the desired version.
It looks like with some more logic for the second case the "default" remote HEAD can be determined to make the version fully optional. I will look into creating a patch for this in the near future.
from vcstool.
I have created pull request #21 to implement the feature you requested. Can you please give it a try and confirm that it works for your use case?
from vcstool.
Closed by #21.
from vcstool.
Thank you for your work on this. I look forward to testing this version when it makes its way into apt.
from vcstool.
The Debian package is already available: http://packages.ros.org/ros/ubuntu/pool/main/p/python-vcstool/
from vcstool.
Related Issues (20)
- Invocation of command 'import' on client 'hg' failed HOT 2
- submodules usage w/o .gitmodules file HOT 1
- "vcs pull" gets stuck indefinitely
- [feature] option to use hash attached to the relative path instead of the version field
- [feature] self checkout from a branch
- Could not checkout ref '...': fatal: invalid reference HOT 1
- startup time is very long HOT 1
- bad non-descriptive error message 'NoneType' object is not subscriptable HOT 1
- git: vcs import by hash does not work for hashes not in local history HOT 1
- Input data is not valid yaml format: mapping values are not allowed here HOT 5
- [Feature Request] version by author or commit date-time HOT 5
- Import non git tars
- VCS Tool is occasionally causing ssh key errors on enterprise git server HOT 4
- vcs export exits with error if there are local branches that don't track remote branches
- Ignore self signed cert for a specific repository HOT 4
- DeprecationWarning: pkg_resources is deprecated as an API HOT 1
- [feature] Ability to only show errors
- validate fails with commit hash HOT 3
- vcs export --exact-with-tags output fails pre-commit linting rules
- BUG: VCS status does not indicate problems if a tag was force-pushed HOT 4
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from vcstool.