Switching to Git

[Joost van Baal-Ilić]

Hi Tanguy,

On Sun, Feb 24, 2013 at 11:39:09AM +0100, Tanguy Ortolo wrote:
> Joost van Baal-Ilić, 2013-02-24 07:34+0100:
> >We have the script
> >http://anonscm.debian.org/viewvc/debian-flyers/general/translation-check.pl?view=markup .
> >
> >It contains
> >
> ># Read the original CVS/Entries file and extract version from it
> >if (open (CVS_ENTRY,"<CVS/Entries")) {
> >
> >The script is used in
> >http://anonscm.debian.org/viewvc/debian-flyers/general/Makefile?view=markup ,
> >which has:
> >
> ># check up-to-dateness of translations
> >check:
> >    @for l in $(transfiles); do ./translation-check.pl $$l; done
> 
> I see the general point of that, but I am not used to CVS and I do
> not understand Perl very well. This script is clearly made to
> indicate whether or not each translation is up-to-date, but it uses
> some kind of version number for that, is that simply a common CVS
> revision number?

Yes, exactly.  Translations have a comment indicating which version of the
english original they claim to be a translation of.

> I would be able to write a script, certainly not in Perl but rather
> in Python, or perhaps just in shell using the usual Git utilities,
> that could, given two files, compare the dates of the commits that
> modified them last time, for instance:
>     2013-01-14 19:38 $ vim foo
>     2013-01-14 19:40 $ git add foo
>     2013-01-14 19:40 $ git commit
> 
>     2013-02-12 23:24 $ vim bar
>     2013-02-12 23:27 $ git add bar
>     2013-02-12 23:27 $ git commit
> 
>     2013-02-21 20:06 $ ./check-freshness foo bar
>     bar (2013-01-14 19:40) is up-to-date compared to foo (2013-02-12 23:27)
> 
> Do you think that would be suitable?

I'd prefer something else:

> Joost van Baal-Ilić, 2013-02-24 07:34+0100:
>> translation-check.pl comes from the Debian website code.  The
>> www-team likely has a reimplementation.  We should look around for such a thing
>> there.
>> 
>> Check how the www-team does check for
>> up-to-date-ness of translations, and copy their code (assuming it works with
>> git).

Do you have time to search for the script the www-team uses to handle this?
Imho it'd be a waste if we'd implement exactly the same functionality in yet another
way.

>> And even if the conversion to git is done just now, we are still pretty
>> OK.  I feel having the code in git with a broken translation-check.pl is better
>> than the current situation.

I.e.: I'd be happy to have stuff converted to git _now_.

> >and no other code to generate a date.  To me, this looks like the
> >rcsinfo/MyRCS-stuff is just dead code, it is no longer used.  I believe
> >"\usepackage[today,datehyphen]{rcsinfo}" should get removed.
> 
> I think so, I shall try it.

Cool, thanks.

Happy hacking, Bye,

Joost

PS: thanks for maintaining the dokuwiki package!

-- 
I will go before thee, and make the crooked places straight: I will break in
pieces the gates of brass, and cut in sunder the bars of iron     --Isa 45:2