Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to firstname.lastname@example.org.
Bo Berglund wrote: > > > The changes I have done is to modify the source dir so it is a > > > non-CVS dir inside my cvsnt sandbox > > > > > Uh, why? > > > > -Torsten > > That is purely because: > 1) My D: drive is a CD-ROM (the source dir in ths script is on D:). > Thus it cannot be used to store the source files for the script. > > 2) I tend to want to keep all of my software project collected inside > a top folder including the binary results, don't you? In my case I > have the cvsnt checked out sources on my F: drive some ways down the > folder ladder... Well, usually IMO absolute paths have no business in an install script anyway (actually that applies to any kind of source code). Path references should always be either relative or controlled via environment variables (or parameterized in some other way). > So my comment was really to explain that I don't really need to commit > back any changes to the script itself... Maybe not for this round. I was talking in more general terms. Just to make sure there is a (relatively) up-to-date copy of the script available from a central place. Cheers, -- Oliver ---- ------------------ JID: ogiesen at jabber.org ICQ: 18777742 (http://wwp.icq.com/18777742)