[Kde-scm-interest] Amarok move to git broke scripty

[Albert Astals Cid]

A Dilluns, 27 de juliol de 2009, Chani va escriure:
> On July 26, 2009 14:34:08 Albert Astals Cid wrote:
> > A Diumenge, 26 de juliol de 2009, Chani va escriure:
> > > > > if something goes wrong on the pull, scripty will abort, which is
> > > > > bad. in order to fix that I need to redesign findfiles... albert,
> > > > > is there a reason it gathers all the .desktop files from all
> > > > > modules together and then splits them back out again? or can I make
> > > > > it work on one module at a time without pain?
> > > >
> > > > ¿Hmm?
> > > >
> > > > I have no idea why findfiles does that, coolo created it, but i don't
> > > > see why you need to touch findfiles at all to make scripty not abort
> > > > when a pull fails since there's no pulling at all in that file.
> > >
> > > when a pull fails, I'd like scripty to completely ignore that module
> > > for the rest of that run. findfiles currently doesn't give me a way to
> > > do that. I suppose I could still ignore the *results* findfiles gets
> > > for that module, but it'd be nicer to not have it waste time on it at
> > > all.
> >
> > On the other hand why don't you focus on pull not failing and ignore
> > this? I mean why should pull ever fail?
>
> if the server goes down. that's what happened once before.

Hurray for gitorious!

> or if some silly person messes up get_paths.

Hurray for silly people!

> or... hmm, I should check whether it can cope with people rewriting history
> (regular developers won't be allowed to do that, but I'm not sure if it
> might end up being necessary once in a while?)
>
> I don't expect it to happen often at all, but it'd be nice if it didn't
> take down translations for the whole branch if it does.

Why it should take them down? If updating fails it will work over old files 
but i don't see why it would take down translations at all.

I mean, svn has the exact same problem, no? If svn up fails, findfiles works 
over old files, right?

Albert