[pca] auto update for develomp
Glenn Satchell
Glenn.Satchell at uniq.com.au
Mon Feb 23 12:41:26 CET 2009
>Date: Mon, 23 Feb 2009 10:33:49 +0100
>From: Martin Paul <martin at par.univie.ac.at>
>To: "PCA (Patch Check Advanced) Discussion" <pca at lists.univie.ac.at>
>Subject: Re: [pca] auto update for develomp
>
>Hi Paul,
>
>> If I wanted to run the development version of pca and keep it up to date
>> with the latest version, is there an option for that?
>
>Setting the "pcaurl" option (as you already mentioned below) is the
>supported and documented way to do that. If the URL should ever change,
>I would put a redirect in place so the URL is kept valid. With
>"update=develop" I would have to hardcode the URL into pca, which
>doesn't give any advantage either.
>
>If there's any other disadvantage to setting pcaurl which I don't see,
>please let me know.
>
>> You could even have the dev version look for pca-dev.conf, but that may
>> start to complicate things.
>
>Yes, even though I'm working with different versions of pca a lot, I've
>never needed that.
Hi Paul,
What about using --cffile to point to an alternative pca.conf that has
the dev settings in it that you want?
Alternatively you could write a small shell script wrapper called
pca-dev that added all the command line switches to get the dev
versions.
regards,
-glenn
More information about the pca
mailing list