Fix Issue 2473, 10941 - Linux system install instructions incorrect#2306
Fix Issue 2473, 10941 - Linux system install instructions incorrect#2306dlang-bot merged 1 commit intodlang:masterfrom
Conversation
|
I've been saying this for EVER. The correct linux install instructions are "unzip the tarball. use it in place". That stupid page has caused so many newbies so much unnecessary pain. |
|
Using relative paths in the default dmd.conf makes no sense. We should just decide on a global path like |
|
@quickfur relative paths are necessary - otherwise you can't use the dmd binary without "installing" it, which is a major use case, e.g. the install script which is also used by Travis depends on this. |
|
I wouldn't be a D user today if there was insistence on global paths. Relative paths in the config were (and still are, though nowadays I'd just fork it and fix it myself), believe it or not, THE #1 reason I chose Digital Mars back in the day. These compilers just worked while the competition wouldn't even start up. |
|
You're right, I said that too brashly. Actually, even I myself rely on the relative paths. :-D Otherwise my current setup based on git master wouldn't even work. And you're right, too much reliance on global paths is bad (I tried installing two different versions of gcc side-by-side once... it scarred me for life. It's possible, no doubt, but involves black magic that mere mortals have no business dabbling in). |
|
Perhaps a script for installing the correctly-fixed dmd.conf to /etc would be best. Or just suggest all of the alternatives and let the user choose. |
|
There's really no reason to put it in /etc at all. My preference is to just delete these insane instructions and replace them with the real options:
|
|
Sounds good to me. |
|
Though I'd at least put a more detailed description of how installing to /etc works somewhere (not necessarily on this page), should the user prefer to do that. Well, it's more of a documentation of how it would work, rather than something the user would actually do. So that in case somebody screws up his installation, there's at least a google-able document describing how things actually work that he could use to troubleshoot whatever it is he did wrong. |
The installation hint is already part of #2290
It already exists - just at the lower part at the document, because it isn't too important: https://dlang.org/dmd-linux.html#dmd-conf So anything I can still do here? |
Ping. |
The dmd.html page needs serious work and apparentely it always has been like this since 2008!
I wasn't sure on the best way to fix this because the shipped
dmd.conflooks like this:In other words, the shipped
dmd.confcan't be simply copied to/etc/. This means we have the following solutionsa) just tell the user to add it to his
PATHb) advertise to use e.g. a symlink to
/usr/bin/dmdc) provide an alternative
dmd.conffor copy/pasting to/etc/dmd.confd) provide a command to patch the shipped
dmd.confe) suggest to move the entire folder to
/usr/localand symlinkdmdthen...
(the FreeBSD + MacOS sections of this need similar adjustments, but I left them for now until I know how to proceed here)
See also: #2290