On Wed, 25 Feb 2009, Malcolm J. Currie wrote:
>> If fftw is modified then nothing will be done - "do no harm". Clear out
>> all the submodules that update-modules complains about and do nothing
>> else until it runs to completion.
>
> OK, but the issue is to know which files to delete. Clearly, the "rm
> applications/extractor/*" was not a success. After some faffing about I
> was about to get "make clean" to work for fftw, but the fftw directory
> is still modified. I tried clearing out the fftw directory, but it
> still complains that the directory has been modified. When I remove the
> directory,
A list of all the submodules:
% git submodule | awk '{print $2}'
The sure fire way to clear these ready for updating is:
foreach f (`git submodule | awk '{print $2}'`)
rm -rf $f
mkdir $f
end
and update them:
% ./update-modules
but that will remove any work you've done already, so you may want to
cherry pick the submodule list.
> update-modules complains about that directory being an "unitialized
> submodule".
That's good, uninitialised is ready to be initialised and then updated
with actual submodule.
> Are there any more of the sub-module changes in the pipeline? I think I
> should do a fresh download once the dust has settled. This is driving me
> bonkers.
There are no more replacement submodules planned as far as I know, so if
you want to start from fresh it's a good time (there is some possibility
of picking up new submodules for building the Perl modules and maybe even
ORAC-DR, but that shouldn't be as difficult to manage).
Tim and I are also updating the vendor code in a lot of the thirdparty
packages, so you're not free of update-modules yet as those change are
percolated through.
Peter.
|