I've always disliked editing configuration data in [dspace-source] and tried to avoid it. I keep the local source in a branch in a local SVN instance, and I don't like to pollute it with settings for a particular DSpace instance (since we run several off the same sources). I edit configuration files in [dspace] (for various values of [dspace]) and keep [dspace]/config in SVN as a separate project rather than part of the source. What I want to do is to:
1. log onto the production box; 2. edit [dspace]/config/dspace.cfg if necessary; 3. 'svn export' the revision I want to install; 4. 'mvn package'; 5. 'ant -Dconfig=[dspace]/config/dspace.cfg update'; 6. done. Then perhaps go to another box and do the same thing again, with its slightly different [dspace]/config/dspace.cfg If I put local information into [dspace-source], that makes it harder and more error-prone to produce clean patches for sharing. At one point the 'update' Ant target would replace [dspace]/config/dspace.cfg from [dspace-source]/config, so I developed the habit of keeping yet another directory specifically for dspace.cfg versions. (I have quite a number of them for testing various things.) The update behavior has been corrected but I kept the habit. I know that I'm going against established practice here, but I feel strongly that configuration data are NOT part of the product, and that no installation or update script should touch them if they already exist in the target directory. The only time I want an installer to open live config. files for writing is when they don't exist. -- Mark H. Wood, Lead System Programmer mw...@iupui.edu Friends don't let friends publish revisable-form documents.
pgp3J5OQhCyOn.pgp
Description: PGP signature
------------------------------------------------------------------------------ Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev
_______________________________________________ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
