RejectedSoftware Forums

Am 28.10.2013 15:35, schrieb Joseph Rushton Wakeling:

On Mon, 28 Oct 2013 09:00:40 +0100, Sönke Ludwig wrote:

As Jacob already said, there is some controversy about this topic. On
one hand it would be nice to have something like this, but on the other
hand it opens a lot of questions as soon as you want to go beyond a
single dub-bin directory that is added to PATH (things like resource and
configuration files, OS or distribution specific paths etc.).

I think that it may be a bullet that needs to be bitten at some point -- that dub needs to have some way of properly installing and uninstalling resources either locally or system-wide. There's got to be a way of doing it that will work on POSIX and Windows in 99% of cases.

An alternative might be to build in some way for dub to output .deb, .rpm, etc. packages ... ?

The package generation feature would be my favorite. There are a lot of
details that need to be right, including the big issue to specify system
(library) dependencies in a platform and distribution independent way.
PackageKit has been suggested as a starting
point, but that works only for some systems, so we'd have to build some
kind of mapping database for other systems on top.

The other possibility would be to offload all that responsibility to the
package creator, so that system dependencies must be specified per
distribution. That, on the other hand, will most probably reduce the
average number of platforms supported per package.

On Mon, 28 Oct 2013 18:54:46 +0100, Jacob Carlborg wrote:

I think it will be fairly clean if everything (all packages) is self
contained within a single directory.

On POSIX, I'd have thought it would work to have user-local installs in ~/.dub and system installs in /opt/dub (so executables in ~/.dub/bin or /opt/dub/bin, etc.), and installation of dub itself should ensure that these directories are added to PATH. No ... ?