[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

Martin Nowak <code at dawg.eu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |code at dawg.eu

--- Comment #6 from Martin Nowak <code at dawg.eu> ---
(In reply to Andrei Alexandrescu from comment #4)
> 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.

But you'd need one for each different OS.
You could probably cd into the STABLE_DMD dir, then you have a working dmd.conf
in your working dir. Quite a hack IMO, and depends on dub not changing the
working dir.
Or you copy the dmd.conf from the STABLE_DMD into dlang.org before building.

But seriously this discussion just shows that we should change the dmd.conf
search order. When did you ever have such trouble with your gcc specs?
https://github.com/D-Programming-Language/dmd/pull/4256#issuecomment-68931542

> > 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).

Trouble with LATEST is that LATEST changes the moment we tag a new version,
which means we need to fix any dmd version dependent issues/deprecations in
dpl-docs and it's dependencies before tagging a new dmd version.
This still causes a lot of trouble and makes it unnecessarily harder to build a
release, because nobody tests these targets with a recent dmd.
It will hopefully improve when all dependencies and dmd releases become even
more stable and when we autotest dlang.org.

--