Well, there are a couple of things to think about here: We need to distinguish building and installing. Anyone is welcome to build DSpace if he wish, but many sites don't really want to and shouldn't need to. If you're not developing the stock DSpace code then there should be no reason for you to build it other than sheer curiosity.
Who wants a simple installer? New sites with simple requirements, I would suppose. It should cater for them, and get out of the way of people who want to do complex things. That is: using the installer should be optional. I should be able to just unpack the distribution kit(s) somewhere and ignore the installer if I know what I'm doing, and that would be the normal mode of doing something fancy. I agree that an installer program which can handle *every* kind of installation is often the Impossible Dream. It would be bigger than the rest of the product, and too complicated to use comfortably. And comfort is the reason for having an installer program in the first place. However, simple installations can be programmed without a lot of effort and will serve many sites well. -- Mark H. Wood, Lead System Programmer mw...@iupui.edu Asking whether markets are efficient is like asking whether people are smart.
pgpUJxwKyQGc0.pgp
Description: PGP signature
------------------------------------------------------------------------------ Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
