[Kde-scm-interest] initial port of scripty to git is ready

[Albert Astals Cid]

A Dijous, 21 de maig de 2009, Oswald Buddenhagen va escriure:
> On Wed, May 20, 2009 at 10:34:41PM -0500, Matt Rogers wrote:
> > 2. there is no initial git clone to get a working copy if it is
> > missing
> >
> > since I don't know what the layout of the new git repositories
> > is going to look like.
>
> i guess you'd need a crystal ball for that. :)
>
> > 3. There is no 'git push' back into the main repository from scripty's
> > clone
>
> ... which would be preceded by a "git pull --rebase || <start over for
> the files with merge conflicts>", and the whole thing executed in a loop
> until it succeeds.
>
> i'd like to suggest that the commits into the repo be done *way* more
> seldomly than currently, preferably only once per release, because:
> - reading the log of any directory with .desktop, etc. files is quite a
>   pain already
> - with everybody having a complete copy of the repository, we don't
>   really want to have more commits than necessary
>
> actually, i am wondering whether we really *want* scripty to modify
> .desktop files. after all, as all but a few translation are irrelevant
> for almost everybody. alternative approaches would be:

That sentence sounds dangerously like my "i18n is a second citizen in KDE" 
blog.

> - don't put translations into the .desktop files at all. instead, let
>   them specify a catalog file.
>   - that of course implies an amendment of the .desktop file standard
>   - it is kinda resource-hungry at runtime, as just browsing a directory
>     might have to load tens of full-blown catalogs.
>     this makes it kinda infeasible without a (possibly standardized)
>     caching architecture in the file managers. i.e., the complexity is
>     non-trivial.
> - add the translations as a build step, only using the ones for which
>   l10 packages are available. i wonder what the performance impact of
>   this would be?

Though here you improve it a bit.

Albert

> _______________________________________________
> Kde-scm-interest mailing list
> Kde-scm-interest at kde.org
> https://mail.kde.org/mailman/listinfo/kde-scm-interest