Git, the D package manager

[Vladimir Panteleev via Digitalmars-d]

On Monday, 2 February 2015 at 09:25:31 UTC, Mathias LANG wrote:
> On Monday, 2 February 2015 at 09:03:56 UTC, Vladimir Panteleev 
> wrote:
>>
>> Is that so? Won't a security fix entail a version bump, 
>> requiring a change in the requirements file of the parent 
>> project? Also, does Dub really check for updated versions of 
>> libraries online, every time a project is built?
>>
>
> It does.

It actually does a roundtrip every time you build your project???

> You have a broad range of options for specifying which version 
> to use.
> http://code.dlang.org/package-format#version-specs
> If you use Semver correctly, it's a great benefit.

In that case, why is it becoming popular to add 
dub.selections.json as a versioned file to the repository?

>> No, it is not necessary. The directory layout could be 
>> ~/.dub/fruit-1.0.0/fruit/...
>
> What would be the advantage ?

The directory structure would correspond with the package 
structure.

As is required by the language specification:

https://github.com/Hackerpilot/DCD/issues/185

> You should not deal with ~/.dub/.

You have to, if you want to use tools that need to read your 
source code other than dub.

> Note, you can specify local packages:
> "fruits": { "path": "fruits" }
> Works well with git submodules.

I don't see what that would do to help. Would this tell dub that 
there is a package called "fruits" in a directory called 
"fruits"? Because the compiler already assumes that already.