On 7/7/20 11:08 AM, Adam D. Ruppe wrote:
On Tuesday, 7 July 2020 at 13:00:04 UTC, Steven Schveighoffer wrote:
Doing that these days would be silly. You can depend on a specific
version of a repository without problems.
I always have problems when trying to do that. git submodules bring
pretty consistent pain in my experience.
But it probably isn't so bad if the submodule rarely changes.
It's cumbersome in my experience, I do it on some iOS projects that I have.
But as long as you don't touch ANY FILES inside the cloned submodule,
and just use git to update it (i.e. git checkout v1.x when upgrading),
you are just versioning which commit your code depends on.
Xcode makes this difficult because it tries to write some temporary
files inside the submodule, and I have to clear those out before upgrading.
But that problem shouldn't exist here. Like all things git, it's hard
until you figure it out, and then it becomes easy.
Just for 100% control anyway nothing beats copy/paste. Then there's zero
difference between you writing it yourself.
I kinda wish the D upstream were more willing to do that. My view is it
shouldn't be on independent developers to add stuff to Phobos, for
example, instead the Phobos team should just be copying and testing
modules they are interested in on their own.
The problem here is that you are maintaining a separate copy. There is
always the chance that you don't copy it right (e.g. you copy a local
checkout that has some test changes you made, or you copy the wrong
version). Imagine how fun the reviews will be when you have to check
that all the cumulative changes from 1.0 to 1.5 match what the source
repository has.
We have computers and software to do source control for a reason.
-Steve
