[Kde-scm-interest] scripty questions

Chani chanika at gmail.com
Sat May 23 07:05:07 CEST 2009


I have a plan for making scripty accept git modules, but it's bedtime now, so 
I want to dump a bunch of questions here in hte hopes that there'll be answers 
in hte morning :)
there's one possible snag, btw... well, I'll get to that...

first, there are some scripts that don't seem to be called from anywhere.
is merge.sh obsolete? can it be deleted?
repack-pot.pl isn't used right now; can it be deleted?

what calls make_doc_externals? is it just called manually as needed?
what calls createdoctemplates?

what calls process_orphans.sh? why's there a copy of it in l10n-support too? 
why does process_orphans.txt look like nothing has ever been deleted from it?
what's lbundle-check.py? does it read/write files outside of l10n folders?

update_xml is run manually by .. some guy, as needed, right?

why are we extracting messages from qt?

if I was to move the scripty files into their own folder to separate them from 
the non-scripty files, would I have to change anything apart from those files 
and makemessages?

scripty's extract-messages takes care of making rc.cpp from all the ui files - 
but some Messages.sh do that too. is this a bug in those Messages.sh?


now, the problem: documentation/ is full of svn externals. absolutely full of 
them.
if this folder is only used by scripts (and people running the scripts who 
know what they're doing), then I should be able to write a script to fetch the 
code from git. but if translators expect this folder to be full of docbook 
files when checked out, that could be bad, when half those files are in git.
(btw, only a couple of the externals successfully checked out when I tried 
anyways. svn: No such revision 971664 )

the best thing I can think of in that case is asking the translators to run a 
script to update documentation/ after they svn up (or checkout). which isn't 
ideal.
so, do translators need it? if so, is it a big deal to run a script after svn 
up? are there any other ways of dealing with this?
also, the documentation/ folder *is* treated as readonly, right?


-- 
This message brought to you by eevil bananas and the number 3.
www.chani3.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/kde-scm-interest/attachments/20090522/3e8d529f/attachment.sig 


More information about the Kde-scm-interest mailing list