[dmd-beta] dmd 2.063 beta 5

[Walter Bright]

On 5/25/2013 9:01 PM, Nick Sabalausky wrote:
> Heh, ok, I think I understand the problem ;)

<g>

>
> Although I don't think this is important enough to hold up the 2.063
> release, I'm going to see what I can do about a cleaned-up version
> of that script that can go up on github, so we can easily do whatever
> wrt zips.
>
> Couple questions though:
>
> 1. I haven't been closely following the activity/discussions on the
> matter, but do we have git branches now which all the betas and
> releases are built directly from? Is it the "staging" branch of each
> repo?

The 'staging' thing was discarded. Now, all the repos have a "2.063" branch. 
When it is released, there will be a "v2.063" tag on that branch. Bug fixes can 
still be added onto that branch, as well as new point releases as necessary.


>
> 2. Walter: How in the heck is your working directory structure laid
> out? I take it the starting point of your script isn't a single
> directory containing direct checkouts of the "dmd", "phobos",
> "druntime", "tools", "installer", "dlang.org" projects all as sister
> directories to each other.

It's a significantly different structure than on github, as github came much 
later. But that should be irrelevant to your work.

>
> Related note, Something I think may be worth considering for the
> future:
>
> If we could get simple DMD-bootstrapping scripts into the installer
> repo (actually, didn't Andrei already make something like that?), then
> all the other scripts could be written in D itself. The big benefit I
> see to that is dealing with error conditions, prerequisites, usability,
> and multiple platforms (not to mention basic ordinary logic constructs)
> is much, much simpler in D than in shell/bash/batch/etc. I wouldn't
> mind tackling any or all of that in my spare time if there was interest.

I think that's a cool idea.