On Monday, 29 February 2016 at 06:10:17 UTC, Chris Wright wrote:
On Mon, 29 Feb 2016 04:46:13 +0000, mahdi wrote:
[...]
In other words, you want to distribute your source code, but
you don't want to host a publicly accessibly git repository and
don't want to use any of the free git hosting services around.
I'm not sure how this would be an advantage. You don't have to
learn git, I guess? It's less VCS lockin? Though it probably
wouldn't be so hard to add mercurial and svn plugins for dub.
Something that *would* be useful is a command that produces
binaries and, in the case of libraries, D interface files so
people can depend on the library even if the full source code
isn't available. The obvious problem: D is typically compiled
to native code. That means you have to compile once for each
platform. Also, you need a different binary for every set of
version() flags the thing supports. That makes binary
distribution tricky in the general case.
The aim is to make package distribution easier and more
straightforward. If someone has done some development on his
local machine and wants to distribute it, it's better not to
force him to create a repo on Github or ... .
