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

Albert Astals Cid aacid at kde.org
Sun Jul 26 22:37:54 CEST 2009


A Dimarts, 21 de juliol de 2009, Chani va escriure:
> how to tell scripty about a move to git:
>
> 1) on gitorious, give scripty access to your repository (yes, it has an
> account already).
>
> 2) edit l10n-kde4/scripts/get_paths:
>
> a) add your module to the list in list_modules (you guys were part of
> extragear-multimedia, but now you're your own module)
>
> b) add your module to get_path, before the *)
> example:
> 		git-test)
> 			echo git/git-test
> 			;;
>
> c) add your module to get_vcs before the *)
> example:
> 		git-test)
> 			echo git
> 			;;
>
> d) add your trunk-equivalent branch to get_branch before the *)
> example:
> 		git-test)
> 			echo "master"
> 			;;
>
> e) add your git url to get_url before the *)
> example:
> 		git-test)
> 			echo "git at gitorious.org:scripty-with-git/git-test.git"
> 			;;
>
> 3) commit changes and pray that it works ;)
>
>
> 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.

> also, what's the easiest way in bash to remove one module from the module
> list? I guess it's really just one big space-separated string, so some kind
> of string parsing could be used to remove it. or I could be lazy and just
> build a second list of modules, consisting of only the ones that updated
> ok. that'd probably be easier and less error-prone...
>
> oh, and afaik the scripty in branch does not yet support git. only
> trunk/l10n- kde4 has my changes. the branch one needs to be updated before
> amarok can have a second branch for scripty to check.

Let's make sure trunk works first ;-)

Albert


More information about the Kde-scm-interest mailing list