The DUB package manager

Sönke Ludwig sludwig at outerproduct.org
Sat Feb 16 13:21:55 PST 2013


Am 16.02.2013 21:02, schrieb Johannes Pfau:
> This way there are no second class build systems.

I actually think it is indeed _good_ to have a first class build system
for exactly the reason that H. S. Teoh gave. If other build systems
really are on the same level as the standard one, it poses the risk of
fragmentation among different packages and users would possibly have to
install a number of different build tools to build all dependencies.

That said, providing an interface to the dependency information to
better support other build tools definitely is a good thing no matter
which way is taken.

My idea for the things you mentioned (swig, c, etc.) was to have a set
of hooks that can be used to run external tools (invoked before
build/project file generation, before build or after build). That
together with your proposed interface should provide all the necessary
flexibility while putting an emphasis on a standard way to describe the
build process.


More information about the Digitalmars-d mailing list