[Issue 14180] dlang.org: make apidocs-release requires user to hamstring own machine

[via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=14180

--- Comment #4 from Andrei Alexandrescu <andrei at erdani.com> ---
(In reply to Sönke Ludwig from comment #3)
> (In reply to Andrei Alexandrescu from comment #2)
> > (In reply to Sönke Ludwig from comment #1)
> > > So should I just drop the --compiler switch and assume that a working DMD is
> > > found in PATH?
> > 
> > That was the situation before, and there was code that didn't compile
> > depending on what D version was installed on the client machine. FWIW if you
> > remove --compiler, I'll have errors on my machine because my default
> > compiler is HEAD and for some reason can't compile that.
> 
> Hmm, so is there a way to use the one at
> /tmp/.stable_dmd-2.066.1/dmd2/osx/bin/dmd without it reading /etc/dmd.conf?

One option is to use the -conf= flag for dmd that Martin added recently. Of
course that's not available with 2.066 :o).

Another possibility is to plant a dmd.conf file in the working directory.
Martin disagreed with that. I happen to think that's a good solution (in fact a
great solution considering right now things are just broken) but I defer to him
because he's the release czar.

> Or would the one at $(DMD_DIR)-${LATEST}/src/dmd be a better choice? The
> relevant code in posix.mak doesn't look familiar to me, so I'm a little
> unsure what the intention has been to do it exactly like it is now.

I, too, think that's better but again I got vetoed by Martin because "it's just
one more short download".

Martin - guess you need to fix this :o).

--