I just released a new version of DVM, 0.4.4. The most important change for this release is that DVM now will try to first download the platform specific package.

For everyone already using DVM, please update to this version because the current release of DMD is most likely that last one to provide the cross-platform package DVM has been using so far.

This release fixes a bug (issue 31) on Windows causing the default compiler not persist. This release also comes with experimental support for FreeBSD (using Bash).

For pre-compiled binaries and changelog (or below) see [1].
DVM is also now available via Dub [2].

For those not familiar with DVM:

DVM allows you to easily download and install D compilers and manage different versions of the compilers.

Changelog:

Version 0.4.4
  New/Changed Features
   * Experimental support for FreeBSD (using Bash)
   * Download DMD using platform specific archive if available
   * Support for installing release candidates
   * Download DMD from `downloads.dlang.org` (fallback to `ftp.digitalmars.com`)
   * Set a user agent when fetching compilers. The user agent will be in the form of `dvm/<version> (<architecture>-<operating system>)`

  Bugs Fixed
   * [Issue 31](https://github.com/jacob-carlborg/dvm/issues/31): Windows: default compiler does not persist

[1] https://github.com/jacob-carlborg/dvm/releases/tag/v0.4.4
[2] http://code.dlang.org/packages/dvm

-- 
/Jacob Carlborg

On Sunday, 13 September 2015 at 16:26:04 UTC, Jacob Carlborg wrote:
> I just released a new version of DVM, 0.4.4. The most important

I am on Windows 10. Is:

dvm --latest install

a valid way to get the latest dmd? When I try that I get an exception

--------------------------------------
dvm --latest install
An unknown error occurred:
tango.core.Exception.IOException@C:\Users\doob\AppData\Roaming\dub\packages\tango-1.0.1_2.067\tango\core\Exception.d(59): truncated response
----------------
0x004421D4
0x00441ECD
0x00441688
0x0040A637
0x0040A4F5
0x004334EA
0x0044FC5B
0x0044FB71
0x004021E8
0x769B8484 in BaseThreadInitThunk
0x77252FEA in RtlValidSecurityDescriptor
0x77252FBA in RtlValidSecurityDescriptor

On Monday, 2 July 2018 at 06:21:53 UTC, Tony wrote:
> On Sunday, 13 September 2015 at 16:26:04 UTC, Jacob Carlborg wrote:
>> I just released a new version of DVM, 0.4.4. The most important
>
> I am on Windows 10. Is:
>
> dvm --latest install
>
> a valid way to get the latest dmd? When I try that I get an exception
>


Seems unmaintained. Try Cybershadow's Digger which can handle building several versions of DMD too (https://github.com/CyberShadow/Digger), even from locally served webpage as UI.

On Monday, 2 July 2018 at 07:12:47 UTC, Basile B. wrote:
> On Monday, 2 July 2018 at 06:21:53 UTC, Tony wrote:
>> On Sunday, 13 September 2015 at 16:26:04 UTC, Jacob Carlborg wrote:
>>> I just released a new version of DVM, 0.4.4. The most important
>>
>> I am on Windows 10. Is:
>>
>> dvm --latest install
>>
>> a valid way to get the latest dmd? When I try that I get an exception
>>
>
>
> Seems unmaintained. Try Cybershadow's Digger which can handle building several versions of DMD too (https://github.com/CyberShadow/Digger), even from locally served webpage as UI.

There's this too https://dlang.org/install.html.
Maybe it would work with w10 linux subsystem, i cant say by complete lack of win10 experience.

On Monday, 2 July 2018 at 07:12:47 UTC, Basile B. wrote:
> On Monday, 2 July 2018 at 06:21:53 UTC, Tony wrote:
>> On Sunday, 13 September 2015 at 16:26:04 UTC, Jacob Carlborg wrote:
>>> I just released a new version of DVM, 0.4.4. The most important
>>
>> I am on Windows 10. Is:
>>
>> dvm --latest install
>>
>> a valid way to get the latest dmd? When I try that I get an exception
>>
>
>
> Seems unmaintained. Try Cybershadow's Digger which can handle building several versions of DMD too (https://github.com/CyberShadow/Digger), even from locally served webpage as UI.

OK, thanks! I saw DVM mentioned in a thread recently and I went back and couldn't find it and found this one via a search. The one I saw may have been a very old thread that someone revived.

On 7/2/18 3:36 AM, Tony wrote:
> On Monday, 2 July 2018 at 07:12:47 UTC, Basile B. wrote:
>> On Monday, 2 July 2018 at 06:21:53 UTC, Tony wrote:
>>> On Sunday, 13 September 2015 at 16:26:04 UTC, Jacob Carlborg wrote:
>>>> I just released a new version of DVM, 0.4.4. The most important
>>>
>>> I am on Windows 10. Is:
>>>
>>> dvm --latest install
>>>
>>> a valid way to get the latest dmd? When I try that I get an exception
>>>
>>
>>
>> Seems unmaintained. Try Cybershadow's Digger which can handle building several versions of DMD too (https://github.com/CyberShadow/Digger), even from locally served webpage as UI.
> 
> OK, thanks! I saw DVM mentioned in a thread recently and I went back and couldn't find it and found this one via a search. The one I saw may have been a very old thread that someone revived.

I still use dvm (this version 0.4.4 is the latest I believe).

It still works, at least on OSX. But the errors it throws are not very user friendly, most of the time you get a stack trace.

I've never used the --latest switch (which BTW fails on OSX as well). Likely it's a change in how the metadata is stored on the server. Just install by name:

dvm install 2.080.1

-Steve

On Monday, 2 July 2018 at 18:31:50 UTC, Steven Schveighoffer wrote:

> I still use dvm (this version 0.4.4 is the latest I believe).
>
> It still works, at least on OSX. But the errors it throws are not very user friendly, most of the time you get a stack trace.
>
> I've never used the --latest switch (which BTW fails on OSX as well). Likely it's a change in how the metadata is stored on the server. Just install by name:
>
> dvm install 2.080.1

Thanks, that worked!

It doesn't announce where it put the compiler, which turns out to be:

C:\Users\<username>\AppData\Roaming\dvm\

On 2018-07-03 03:34, Tony wrote:

> Thanks, that worked!
> 
> It doesn't announce where it put the compiler, which turns out to be:
> 
> C:\Users\<username>\AppData\Roaming\dvm\

You're not supposed to know where it puts the compiler. You're activating it with "dvm use <version>" where "<version>" is the version you want to activate. This will persist for the end of the shell session. To set a default compiler use "dvm use <version> -d". This allows to use separate versions simultaneously in different shell sessions. See the usage information [1].

[1] https://github.com/jacob-carlborg/dvm#use-a-compiler

-- 
/Jacob Carlborg

On Wednesday, 4 July 2018 at 19:14:57 UTC, Jacob Carlborg wrote:
> On 2018-07-03 03:34, Tony wrote:
>
>> Thanks, that worked!
>> 
>> It doesn't announce where it put the compiler, which turns out to be:
>> 
>> C:\Users\<username>\AppData\Roaming\dvm\
>
> You're not supposed to know where it puts the compiler. You're activating it with "dvm use <version>" where "<version>" is the version you want to activate. This will persist for the end of the shell session. To set a default compiler use "dvm use <version> -d". This allows to use separate versions simultaneously in different shell sessions. See the usage information [1].
>
> [1] https://github.com/jacob-carlborg/dvm#use-a-compiler

I should have done a little more reading. Thanks, and thanks for writing it!