Bug 18808 – dmd not found after installation using script
Status
RESOLVED
Resolution
WONTFIX
Severity
critical
Priority
P1
Component
installer
Product
D
Version
D2
Platform
x86_64
OS
Linux
Creation time
2018-04-29T11:50:04Z
Last change time
2021-11-27T15:33:45Z
Assigned to
No Owner
Creator
Lance Bachmeier
Comments
Comment #0 by lance — 2018-04-29T11:50:04Z
If I install using the script
curl -fsS https://dlang.org/install.sh | bash -s dmd
It gives the message
Run `source ~/dlang/dmd-2.079.1/activate` in your shell to use dmd-2.079.1.
This will setup PATH, LIBRARY_PATH, LD_LIBRARY_PATH, DMD, DC, and PS1.
That works until you close the current terminal. As soon as you use a new terminal, you get
Command 'dmd' not found
On Ubuntu 18.04. I put the severity at critical because the installation process needs to work.
Comment #1 by 4burgos — 2018-06-01T17:29:36Z
Not sure if this is what you're looking for, but still - the usual process with `source`-ing some configuration is that it applies only to the current terminal. If you want it to work in other terminals, add that line to the `~/.bashrc` or `~/.zshrc`
Comment #2 by lance — 2018-06-01T20:12:34Z
That is almost certainly correct. I guess the point is that we shouldn't call something an official install script if it doesn't do a proper installation. If the user has to manually run that command every time they use DMD, or figure out for themselves how to fix it, the installer isn't doing its job.
Comment #3 by dlang-bugzilla — 2018-06-01T23:23:14Z
There is no single correct way to permanently change the system configuration so that dmd ends up in PATH on Linux / Posix, as that is the job of the distribution's package manager.
The actionable here is to improve the message to let them know that the effect is temporary, and they can add the line to their configuration if they want to make it permanent.
Comment #4 by lance — 2021-11-27T15:33:45Z
I think this should be closed. There's no way to do what I wanted it to do when I created this.