On Wednesday, 22 June 2016 at 10:18:01 UTC, Sönke Ludwig wrote:
Am 21.06.2016 um 00:37 schrieb Basile B.:
You should add a system to support example files, without
For example in a static library, something that would indicate
package in which the file resides is itself a dependency but
to be downloaded:
dependency "this" (or dependency "../..")
from ex1 you should be able to locate the package by using
until a dub.json is found. Maybe that if the dep value is a
path that leads to a description this works too.
This currently works using
dependency "package" path="../../"
I'd like to avoid making this smarter, because currently (sub)
packages are all logically distinct, which helps a lot to keep
the internal logic simple in various places. An exception to
this rule is that versions of sub packages are locked to the
version of the parent package, which causes quite some
complications in the dependency resolution algorithm, which in
turn has often been a source of bugs.
Do "single-file packages" have a special name, ie official, e.g
if I want to add a menu item for this ?
- Compile and run single file DUB package
- Compile and run monolithic DUB package
I also think to "runnable DUB module" or "DUBable module"