Re: [squid-users] upgrading 2.4stable7 to 2.5stable2

Tay Teck Wee wrote:
>
> Hi,
>
> currently upgrading from squid 2.4stable7 to
> 2.5stable2 on a linux RH7.3.
>
> present directory structure:
> source files in /usr/local/src/squidXXXXX
> squid directory in /usr/local/squid
>
> It seems like if I were to just untar 2.5stable2 in
> the same directory as the previous version,
> i.e./usr/local/src, after installing the new version,
> some duplicate files and directories will exist in
> different places, i.e. squid executable, log dir, etc.
>
> So besides
> 1)a clean rm -rf /usr/local/squid of the existing old
> squid version directory before installing the new
> version
> and
> 2)moving into each of the directories after installing
> the new stable over the old stable and deleting the
> duplicate files.
> is there any other way which is better? Which is
> recommendated? Thanks.
>
 Basically, the most 'virgin' solution is to, use
 another :

   --prefix=another_squid_dir

 during configure.

 Then 'make install' after make will never lead to
 any 'location conflicts' en squid.conf
 can be edited to use 'old' cache dir(s) without
 any problems,for instance.

 I too am faced by trying to keep squid 'into one account'
 so to speak.

 I solve this by symbolic links,afterwards fooling
 it somewhat, so my main squid top account looks like this :
 
lrwxrwxrwx 1 squid squid 15 Mar 20 18:49 bin ->
bin.2.5.STABLE2
drwxrwxr-x 2 squid squid 4096 Mar 2 17:58 bin.2.5.STABLE1
drwxrwxr-x 2 squid squid 4096 Mar 20 19:01 bin.2.5.STABLE2
drwxrwxr-x 34 squid squid 4096 May 6 06:46 cache0
drwxrwxr-x 34 squid squid 4096 May 6 06:46 cache1
drwxrwxr-x 34 squid squid 4096 May 6 06:46 cache2
drwxrwxr-x 34 squid squid 4096 May 6 06:46 cache3
lrwxrwxrwx 1 squid squid 15 Mar 20 18:49 etc ->
etc.2.5.STABLE2
drwxrwxr-x 2 squid squid 4096 Mar 8 12:05 etc.2.5.STABLE1
drwxrwxr-x 2 squid squid 4096 Mar 21 10:48 etc.2.5.STABLE2
lrwxrwxrwx 1 squid squid 19 Mar 20 18:49
libexec->libexec.2.5.STABLE2
drwxrwxr-x 2 squid squid 4096 Sep 26 2002
libexec.2.5.STABLE1
drwxrwxr-x 2 squid squid 4096 Mar 20 18:48
libexec.2.5.STABLE2
drwxrwxr-x 3 squid squid 4096 Aug 2 2001
libexec.etc.2.4.STABLE1.20010801
drwxrwxr-x 2 squid squid 4096 May 6 06:46 logs
lrwxrwxrwx 1 squid squid 15 Mar 20 18:49 man ->
man.2.5.STABLE2
drwxrwxr-x 3 squid squid 4096 Sep 26 2002 man.2.5.STABLE1
drwxrwxr-x 3 squid squid 4096 Mar 20 18:48 man.2.5.STABLE2
lrwxrwxrwx 1 squid squid 17 Mar 20 18:50 share ->
share.2.5.STABLE2
drwxrwxr-x 4 squid squid 4096 Sep 26 2002
share.2.5.STABLE1
drwxrwxr-x 4 squid squid 4096 Mar 20 18:48
share.2.5.STABLE2
drwxrwxr-x 3 squid squid 4096 Mar 20 18:48 var

 So, when I need to upgrade, I can just remove all links,
choose,and do a configure with the prefix path remaining the
top of the squid account :

 % make install

 will make squid make it's expected dirs again.
 Such as : - bin
             - etc
             ....

 Just renaming (bin to bin.2.5.STABLE3,etc..) for instance and using my
links
 again,gives me some simple control concerning 'version management' and
 the ability to quickly 'fallback' if something goes wrong
 with a new version, for instance.

 M.

 
> Regards,
> Newbie
>
> __________________________________________________
> Do You Yahoo!?
> Promote your business from just $5 a month!
> http://sg.biztools.yahoo.com

-- 
 'Love is truth without any future.
 (M.E. 1997)