Am 14.02.2014 20:46, schrieb Jacob Carlborg:
On 2014-02-13 21:38, Sönke Ludwig wrote:
I mean a path to a cloned working copy, not a local "git remote".
Git can clone from a cloned working copy as well.
I know, what I meant was the role it plays - being used as a local
directory to work on or as a source for a git clone/push/pull command.
That would avoid the burden for DUB to perform the clone/checkout
Dub could of course check if it's a local path.
, possibly managing credentials etc. and provide full flexibility for
the user.Right.
DUB wouldn't even have to know what branch/tag is checked out and any VCS
would work.Right. I'm not against supporting a local path but I think supporting
arbitrary git repositories would be nice as well. Bundler (a tool used
by Ruby projects) supports gems (which would correspond to a package in
the dub registry), git repositories and local file paths. It also
supports "shortcuts" for github repositories. When using a git
repository it will by default used the default branch.
Ah okay, I didn't think of combining the version pinning with this. My
only concern is when you want to check in the pinned versions, but have
different requirements for developers on the team vs. external users.
But I guess you just wouldn't commit the development pinning in that case.
My idea was originally to separate the two, but of course they would
still interfere with each other and it may actually not be the ideal
approach.