To the LDC maintainers:

Thanks for your excellent work on LDC!

I have prepared an installer of Visual D that comes with both DMD and LDC, so there is no hassle for new users to get up and running (at least if they use Visual Studio). I'm planning to add Visual D to the Visual Studio Gallery to make it discoverable from inside Visual Studio, too.

Before going live I think it might be good to ask: Is it ok with you to distribute LDC with Visual D?

Rainer

On Friday, 31 May 2019 at 07:23:36 UTC, Rainer Schuetze wrote:
> To the LDC maintainers:
>
> Thanks for your excellent work on LDC!
>
> I have prepared an installer of Visual D that comes with both DMD and LDC, so there is no hassle for new users to get up and running (at least if they use Visual Studio). I'm planning to add Visual D to the Visual Studio Gallery to make it discoverable from inside Visual Studio, too.
>
> Before going live I think it might be good to ask: Is it ok with you to distribute LDC with Visual D?
>
> Rainer

Sounds great, thx for your work.

Pls provide some more details - will there be a fixed bundled version, or will the installer download the latest stable version on demand? What package is it, the official multilib one?

On 31/05/2019 09:36, kinke wrote:
> On Friday, 31 May 2019 at 07:23:36 UTC, Rainer Schuetze wrote:
>> To the LDC maintainers:
>>
>> Thanks for your excellent work on LDC!
>>
>> I have prepared an installer of Visual D that comes with both DMD and LDC, so there is no hassle for new users to get up and running (at least if they use Visual Studio). I'm planning to add Visual D to the Visual Studio Gallery to make it discoverable from inside Visual Studio, too.
>>
>> Before going live I think it might be good to ask: Is it ok with you to distribute LDC with Visual D?
>>
>> Rainer
> 
> Sounds great, thx for your work.
> 
> Pls provide some more details - will there be a fixed bundled version, or will the installer download the latest stable version on demand? What package is it, the official multilib one?

The installer comes with latest multilib release preinstalled (currently 1.15.0), but Visual D looks for updates via the github API.

The user can select whether stable or pre-releases should be checked. The 7z package is downloaded and unpacked into a common root folder (it would be nice if the current naming conventions and folders in the archive are kept ;-))

On Friday, 31 May 2019 at 08:00:53 UTC, Rainer Schuetze wrote:
> The installer comes with latest multilib release preinstalled (currently 1.15.0), but Visual D looks for updates via the github API.

Ah, nice. We also have http://ldc-developers.github.io/LATEST[_BETA] to check the latest versions (e.g., those are used by Travis for `d: ldc[-beta]`).

> it would be nice if the current naming conventions and folders in the archive are kept ;-)

Heh, yeah that's the reason I haven't switched to semver-compatibility for beta releases (`-beta.1` vs. `-beta1`)...

On 31/05/2019 10:07, kinke wrote:
> On Friday, 31 May 2019 at 08:00:53 UTC, Rainer Schuetze wrote:
>> The installer comes with latest multilib release preinstalled (currently 1.15.0), but Visual D looks for updates via the github API.
> 
> Ah, nice. We also have http://ldc-developers.github.io/LATEST[_BETA] to check the latest versions (e.g., those are used by Travis for `d: ldc[-beta]`).

This is similar to dmd, but it needs more guessing what the actual file name is.

>> it would be nice if the current naming conventions and folders in the archive are kept ;-)
> 
> Heh, yeah that's the reason I haven't switched to semver-compatibility for beta releases (`-beta.1` vs. `-beta1`)...

I don't think that would be a problem. It's currently required that the top level folder in the archive has the same name as the archive itself.

On Friday, 31 May 2019 at 07:23:36 UTC, Rainer Schuetze wrote:
> To the LDC maintainers:
>
> Thanks for your excellent work on LDC!
>
> I have prepared an installer of Visual D that comes with both DMD and LDC, so there is no hassle for new users to get up and running (at least if they use Visual Studio). I'm planning to add Visual D to the Visual Studio Gallery to make it discoverable from inside Visual Studio, too.
>
> Before going live I think it might be good to ask: Is it ok with you to distribute LDC with Visual D?
>
> Rainer

No it would not be ok distribute LDC with visual studio for me. I like LDC because it is stand alone, you can just put it somewhere without any installer and it works. Also Visual D is Windows only but LDC works with many architectures, so for many Visual D would just be extra baggage.

I think perhaps you meant to bundle Visual D with LDC or DMD? That could perhaps be a possibility or the installer gives the user the option to download DMD or LDC.

On Friday, 9 August 2019 at 07:29:20 UTC, IGotD- wrote:
>
> No it would not be ok distribute LDC with visual studio for me. I like LDC because it is stand alone, you can just put it somewhere without any installer and it works. Also Visual D is Windows only but LDC works with many architectures, so for many Visual D would just be extra baggage.

He is not asking to ship Visual D in the LDC distribution. He's asking if it's okay to include LDC in the Visual D distribution:

"I have prepared an installer of Visual D that comes with both DMD and LDC"

>
> I think perhaps you meant to bundle Visual D with LDC or DMD?

The way the verb "bundle" is typically used, "bundle A with B" means putting A inside the B package. (The same can be said about your usage of "distribute" in "distribute LDC with visual studio" in the first paragraph). So no, "bundle Visual D with LDC or DMD" is not what he means.

So if I'm properly reading the intent behind your words, you've got it backwards :-) What you're suggesting is actually what he's asking.

On Friday, 31 May 2019 at 07:23:36 UTC, Rainer Schuetze wrote:
> To the LDC maintainers:
>
> Thanks for your excellent work on LDC!
>
> I have prepared an installer of Visual D that comes with both DMD and LDC, so there is no hassle for new users to get up and running (at least if they use Visual Studio). I'm planning to add Visual D to the Visual Studio Gallery to make it discoverable from inside Visual Studio, too.

This is all pretty great Rainer,  +1 from me!

-Johan