On 06/06/2015 09:16 AM, Jacob Carlborg wrote:
On 2015-06-05 15:17, Steven Schveighoffer wrote:
The source of the package does. code.dlang.org can create this
automatically.
I see two problems with this:
1. Does the registry (code.dlang.org) really know which files a Dub
package contains? I would guess the registry mostly contains information
where to find the source for a package, i.e. GitHub
Rubygems, for example, on the other hand would be able to do this
because a Ruby gem (package) is ZIP archive with all the sources for the
package included. Also, when building a gem the package description is
"compiled", that is, all shell globs are expanded to locate all files.
2. It's possible to have a file with a completely different module name
in D
Even if that stuff isn't currently known to code.dlang.org, it'd all be
easy for it to obtain:
$ mkdir some_temp && cd some_temp
$ git clone package_URL dir && cd dir
$ dmd (flags dub already knows) -v | grep import
Would only need to do that when it detects a new version tag (which it
already detects).
