Hi Marcin
It was obviously added originally because there was a limit to the length
of the PATH variable (presumably there still is), so repeated invocations
of setup scripts could take you over the limit. Ideally the script should
remove old versions from the PATH, not just prepend the new one, but
there's no easy way to make that completely general. David's
CCP4Dispatchers script would seem to offer the best solution.
So I would leave it as it is, the cure may be worse than the disease!
Thanks
-- Ian
On 29 April 2014 12:47, Marcin Wojdyr <marcin.woj...@diamond.ac.uk> wrote:
> On Mon, Apr 28, 2014 at 03:51:57PM +0100, Ian Tickle wrote:
> > Harry,
> >
> > I've run into this problem before with other programs when I switch
> between
> > v6.3 & v6.4. I think the problem is this code in ccp4.setup-sh:
> >
> > if [ `expr ":${PATH}:" : ".*:${dir}:"` -eq 0 ]; then
>
> We can remove this condition if it does more harm than good.
> Marcin
>
> --
> This e-mail and any attachments may contain confidential, copyright and or
> privileged material, and are for the use of the intended addressee only. If
> you are not the intended addressee or an authorised recipient of the
> addressee please notify us of receipt by returning the e-mail and do not
> use, copy, retain, distribute or disclose the information in or attached to
> the e-mail.
> Any opinions expressed within this e-mail are those of the individual and
> not necessarily of Diamond Light Source Ltd.
> Diamond Light Source Ltd. cannot guarantee that this e-mail or any
> attachments are free from viruses and we cannot accept liability for any
> damage which you may sustain as a result of software viruses which may be
> transmitted in or with the message.
> Diamond Light Source Limited (company no. 4375679). Registered in England
> and Wales with its registered office at Diamond House, Harwell Science and
> Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
>
>
>
>
>
