Am 21.06.2016 um 06:42 schrieb Guido:
Dub doesn't really work like other package managers. When I load a package:
dub fetch scriptlike
It stores it someplace and doesn't say where. You have to run 'dub list'
to figure out where. That's is very different than other packages. It
deserves a bigger mention in the meager documentation.
I've been trying to init a project using the command
dub -init -f sdl trickproject
-or-
dub -f sdl -init trickproject
It must be "dub init -f sdl", without the dash in front of "init".
Otherwise it looks correct.
and nothing seems to parse.
So, I look at the source code for the format option and see this:
args.getopt("f|format", &m_format, [
"Sets the format to use for the package description file. Possible
values:",
" " ~ [__traits(allMembers, PackageFormat)].map!(f => f ==
m_format.init.to!string ? f ~ " (default)" : f).join(", ")
]);
It doesn't look straightforward at all. Not sure why there is so much
complexity on this particular commandline option, but shouldn't these
command options work the way I have them?
The complexity just comes from dynamically determining the default file
format (to avoid it getting out of sync).
