Re: udd/blends_metadata_gathener.py hints
On Tue, Oct 22, 2013 at 12:08:13AM +0300, Emmanouil Kiagias wrote:
> > In short: Great job with a minor missing bit (handling of deleted tasks).
> :-) thanks for your good words. Also thanks for mentioning the handling of
> deleted/renamed tasks(I totally forgot that).
> I fixed it and now the deleted/renamed tasks are removed from UDD once the
> blend_metadata_gathener run.
> As you said I keep a list of successfully imported tasks and afterwards I
> remove any task which does not exist into the list.
Thanks for implementing (not checked yet, will test soon).
> Shouldn't we also handle the same way deleted/renamed Blends? (a not so
> often case but it can happen)
> In case of blends-all arguement (which updates all the Blends) we keep all
> the successfully imported Blends to a list and then remove the ones which
> do not exist to the latter.
Well, I think that's a bit tricky. I realised that there are sometimes
problems with reading the repositories which could be another reason for
a not available but not deleted Blend. IMHO handling deleted Blends is
a manual process. We need to clean it up from UDD config file anyway and
thus a manual cleanup from the database should not be so hard. So I
would not do any automatic means here.