Angus Leeming <[EMAIL PROTECTED]> writes:
| It makes sense to have a single "master" repository of the information | in the blanket and in the credits files and to use a script to | generate the "slave".
| I think we both agree with everything up to this point, right?
yes
| Given that the .php files currently contain more info, I created a | script to create the equivalent .txt files. Ie, the "master" here is | blanket-permission.php file and the "slave" is blanket-permission.txt.
| You'd like the "master" to be blanket-permission.txt and to be able to | create the "slave" blanket-permission.php.
Not necessarily blanket-permission.txt, but a file that resides in lyx-devel. The permissions is about who has given permission to use their code under gpl in the lyx code. And all the lyx code is in lyx-devel.
| Ditto for the credits | files. Fine. Be my guest. But before you do so, please have a look at | the .php files. Maintaining them is a piece of cake because all | formatting is generated separately from the storage of the data.
Right... so why does the data have to be in the php file?
and passthru of the data to the php logic should do it... "cvs checkout -p blanket-data-file lyx-devel" gives you the file on stdout.
So, a raw data file, to be stored in lyx-devel, containing entries of the form:
<contribution>
<name>Maarten Afman</name>
<contact>info () afman ! net</contact>
<permission>
<licence>GPL</licence>
<title>Fwd: Re: The LyX licence</title>
<archive_id>m=110958096916679</archive_id>
<date>27 February 2005</date>
</permission>
<credit>
Dutch translation team member
</credit>
</contribution>and (python?) scripts to generate credits.php, blanket-permission.php, and lib/CREDITS?
Angus
