envy for "Writing Go Packages"

Walter Bright newshound1 at digitalmars.com
Fri May 7 16:23:08 PDT 2010

Johan Granberg wrote:
> Walter Bright wrote:
>> Johan Granberg wrote:
>>> Walter Bright wrote:
>>>> Jacob Carlborg wrote:
>>>>> Should it also contain something similar to rdmd?
>>>> I kind of like the idea that it shouldn't install D packages, but rather
>>>> cache them from the web repository. It would be convenient because:
>>>> 1. who actually cares about installing the packages
>>> If I was administering a server or multiuser system or linux distribution
>>> I would care, being able to install packages and libraries globaly for
>>> all users easily can be important.
>> The caching should handle that transparently.
> I have yet to see a system where that works.

I think the internet browser is an example.

? How can an administrator chose
> to install a set of libraries in such a setup?

Essentially, he doesn't, because the libraries are not installed. The build 
process looks in the temporary cache for the files, and uses them if they're 
there, otherwise it downloads them off the network and puts them in the 
temporary cache. They are never actually installed.

> Will it still work if the net conectivity is not always present (laptop).

No, it will not, unless the files happen to already be in the cache. The builder 
will look in the cache first for the files.

> Can a linux distribution
> use that to ensure that some libraries are always pressent?

If that is desired, then they can be actually installed by the administrator.

> Consider that users might not have the dissk quota to allways have their own
> copies of every library imaginable installed.

Being a cache, the least recently used library can always be kicked out, and 
then reloaded as necessary. Think of it working like the temporary cache for 
your browser.

> Experiance from working with debian systems is that the languages that tries
> to make their own solutions for automatic handling and caching and so on
> fails badly, while those integrating/packaging as deb packages works fine.
> Problems seems to apear either when trying to install for all users or when
> installing in a users home directory.

These problems are all sidestepped because the libraries won't be installed. 
It's a wholly different way of doing things.

More information about the Digitalmars-d mailing list