Yes, in it's simplest form you do a git pull and note which libraries/applications have been updated. Then you remove just those manifest files.

Similarly the "make build support" is only needed if the build support tools have been updated. Its main role is to run ./update-modules which makes sure the submodules are synced up (which can also be done as "git submodule update" if you know what you are doing.

Tom - any thoughts on putting molly on github?

Tim Jenness

On Thu, Jan 30, 2014 at 11:54 AM, David Berry <[log in to unmask]> wrote:

SSN/78

http://www.astro.gla.ac.uk/~norman/star/ssn78/ssn78.htx/

has a useful FAQ for things like this. The answer is:

% git pull
% rm /star/manifests/* (replacing /star with something appropriate)
% make buildsupport
% make world

David

On 30 January 2014 17:46, Tom Marsh <[log in to unmask]> wrote:
> I have just run a 'git pull' to refresh my starlink sources since someone here is suffering from a kappa bug I know to be fixed. My question, sorry that its probably rather elementary, is where do I start the re-installation from out of the standard:
>
> ./bootstrap
> make configure-deps
> ./configure -C
> make world
>
> sequence for an installation-from-scratch? Should I play safe and start right from the beginning?
>
> Tom