Am Tue, 11 Apr 2017 15:03:36 +0000 schrieb qznc <q...@web.de>: > On Tuesday, 11 April 2017 at 12:56:59 UTC, Jonathan M Davis wrote: > > But if we just use dub - which _is_ the official packaging and > > build tool - then we avoid these issues. Ideally, the compiler > > and dub would be part of the distro, but libraries don't need > > to be. And it sounds like that's basically how the Go and Rust > > folks want to function as well. So, it would make sense for > > these languages to simply not have their libraries be included > > in distros. The build tools are plenty. > > This is not compatible with Debian. Debian requires to include > *everything*. You must be able to build every package without > network access only from source packages. > > Essentially, somebody must fix this dub issue: > https://github.com/dlang/dub/issues/838
I created a similar issue 3 years ago: https://github.com/dlang/dub/issues/342 A key point is how environment variables that everyone agreed upon made "make" a flexible build tool, being able to use a user specified compiler, installation directory, compiler flags and more. This flexibility is relied on by Linux packaging tools to produce binaries for a specific target. Then there is the problem that at some point you rely on non-Dlang libraries that only the system package manager can provide and update. In the past this always ended in the system package manager winning over the language tool as the common program to update and clean the system. Dicebot and bioinfornatics (Fedora) felt that dub was for developers and wasn't tailored to system administration at that time. p0nce, s-ludwig and markos (Debian) also gave input and the net result was: A Makefile generator for dub shall be written that exposes the desired environment variables and can be used by existing Linux package managers. -- Marco
