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 sales@march-hare.com.
Yes, I agree a bout the paths. Source script location is now a few levels down from the cvsnt top
and it refers to D:\cvsbin as the binaries location. I changed it to point to a folder
named cvsnt but located inside the cvsnt module ({cvsnt}/cvsbin
Thus the paths from the script poit of view could be set as ..\..\cvsbin.
The compression thing is a bit harder though, because I don't want to upgrade my Inno
because we use version 4.1.5 in several cases where I am involved and upgrading
may cause some non-wanted effects. In any case the only new functionality Tony
has used is the extra compression that gains a few % in file size. I commented out
these and all was working fine aftrewards.
I will look into the paths business when I get home tonight.
/Bo
-----Original Message-----
From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org]On Behalf Of Oliver Giesen
Sent: den 13 december 2004 09:17
To: cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook
Subject: Re: [cvsnt] Re: Possible to build InnoSetup installationusingdownloaded binaries?
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)
_______________________________________________
cvsnt mailing list
cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook
http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt https://www.march-hare.com/cvspro/en.asp#downcvs