On Fri, 20 Sep 2013 07:43:55 GMT, Jacob Carlborg wrote:
- For that to work they need to be "installed". That is, compiled and put in some directory, somewhere. That's what I've been talking about all along. I have never said they need t be put in some standard search path, i.e. /usr/lib. Although it is convenient to put applications in PATH, some way or another.
They can be compiled in the very same git clone directory. As I have said, convenient syntax sugar on top of git clones.
- That doesn't work for applications
Works at least in Linux:
PATH=$PATH:/path/to/my/clone/dir dub build
No need to pollute normal namespace, clean and hygienic.
A problem with some OS package managers is that they are so religious so they won't even add a package if it's not following the appropriate licensing. Some package managers won't add DMD due to this.
Then those distros won't have that software. It is their chose and we shouldn't interfere. If users won't agree with that restriction, they will change the distro. Why force software they don't want?
Actually, I have heard of quite mature generic package manager implementations for both Mac and Win, those just don't get any traction / recognition.
As long it's not installed by default it cannot be relied on.
dub is not installed by default too