envy for "Writing Go Packages"

[Lutger]

BCS wrote:

> Hello Walter,
> 
>> You just type the correct package name in the
>> import declaration, and the compiler system takes care of the rest.
> 
> How about a package->source mapping?
> 
> dmd -I my.corp=http://mycorp.com/sourcerepo
> 
> import my.corp.foo; // looked for at http://mycorp.com/sourcerepo.foo.d
> 
> that way when things move, or corps merg, you only need to update the
> mappings.
> 

I like that idea, naming specific remote locations of a package all over the 
place in the source code seems a bit flaky. 

This way you can also more easily specify whether you want to use a local 
install only, download as needed, or a 'lazy-install' which installs as 
needed, checking for updates, etc. It starts to look a bit like dsss :)

The specific package -> source mappings could located in any one of:
- in a pragma
- on the command line
- in a repository listing, either remotely or locally specified