Windows DMD installer

[Vladimir Panteleev]

On Sun, 28 Jun 2009 23:38:27 +0300, Stewart Gordon <smjg_1998 at yahoo.com>  
wrote:

> How is the set of libraries that your installer can install going to be  
> maintained?  Will anyone be able to contribute?

Since this is a community project, it's important not to make any  
component dependent on a single party. I was thinking of something like  
DSSS's system, where package maintainers can register and maintain  
installation/uninstallation "recipes" (not unlike GoboLinux).

> The ideal, however, is to have it so that the user can paste in the URL  
> of any D library and the installer'll install it.  However, until and  
> unless we can standardise how to package a library for download, the  
> user would have to guess whether the installer supports the particular  
> library's way of doing it.

We can do this for libraries containing dsss.conf files.

> Why not install all third-party libraries under a common base path?

Some libraries are packaged with documentation, examples, etc. with the  
actual source in a subdirectory. On my system I resolve this with a  
"packages" directory (containing library packages with the directory  
structure intact) and an "import" directory, which contains symlinks to  
the libraries' source directories. We can't do this since some users still  
use FAT32.

-- 
Best regards,
  Vladimir                          mailto:thecybershadow at gmail.com