Am 15.09.2013 14:16, schrieb Jacob Carlborg:
On 2013-09-15 14:05, Sönke Ludwig wrote:
It sounds like it would fit in well together with "optional" and
"runtime" dependencies. Actually, maybe "optional" could already be used
for this? Sorry if that doesn't make sense ;)Yes, sounds like "optional" could be used for this. When/how does those
get installed?
Any matching package that is available (dub list-installed) will
qualify. So the easiest way is "dub install (optional package name)" to
install user wide.
I couldn't find any documentation for "runtime" here:
http://code.dlang.org/package-format"runtime" sounds like dependencies needed to run the package. This only
sounds useful for binary packages. I.e. three dependencies are required
to build the package but only one dependency to run it.
I was mixing up things there. What I really meant was the planned
support for executable dependencies, such as a parser generator that is
needed to generate the actual source code. But this is actually just an
ordinary dependency with a selected configuration that has "targetType": "executable".
Runtime dependencies, I think, were discussed during the early system
package discussion, but that's a whole different topic of course.