Login | Register
My pages Projects Community openCollabNet

Discussions > dev > Packaging kamikaze

kamikaze-qscm
Discussion topic

Hide all messages in topic

All messages in topic

Re: Packaging kamikaze

Author Guillaume Rousse <Guillaume dot Rousse at inria dot fr>
Full name Guillaume Rousse <Guillaume dot Rousse at inria dot fr>
Date 2006-03-28 00:18:53 PST
Message John W Duprey wrote:
> Neat, is their a package listing online for mandriva, I'd like to see it
> listed. :)
No official package list, you have to browse mirrors for it.

>> What I don't understand, however, is why you did use perl for populating
>> database, and php for exploring it, instead of using a single language?
>>
> Good question. It seemed to me that perl was a more suitable language
> for back end hooks in subversion. I wasn't sure if the CLI version of
> PHP was as common has PERL. Honestly, I don't even think I gave PHP
> consideration to run anywhere but from within the apache environment.
> Another "good" reason for PERL is that I was able to take a large
> portion of the code from example hook scripts - code for parsing the
> results of svnlook, etc.
You're absolutly right about the better fit of perl for general
purposes. My point is that perl is also largelly equal to php for web
applications :)

BTW, you'd rather use CPAN modules as SVN-SVNLook, SVN-Log, etc.. than
those hook scripts that seems to have been written in perl 4 by python
hackers.

> Does it make a difference? I suppose it imposes one more requirement,
> PERL (with DBI support), but you'll find that in just about any
> environment that also has PHP.
The main difference comes from the fact that as long as your
configuration file will be language-dependant, having two different ones
in your application will require two configuration files. And using PHP
make your application mysql-dependant, whereas DBI offers more flexibility.

Re: Packaging kamikaze

Author John W Duprey <jduprey1 at yahoo dot com>
Full name John W Duprey <jduprey1 at yahoo dot com>
Date 2006-03-27 21:18:01 PST
Message Neat, is their a package listing online for mandriva, I'd like to see
it listed. :)

Thank you for the feedback. I'll try to clean things up for .3 which
is slowly nearing completion.
I'll take your thoughts into consideration when packaging things up.


>
> What I don't understand, however, is why you did use perl for
> populating
> database, and php for exploring it, instead of using a single
> language?
>
Good question. It seemed to me that perl was a more suitable
language for back end hooks in subversion. I wasn't sure if the CLI
version of PHP was as common has PERL. Honestly, I don't even think
I gave PHP consideration to run anywhere but from within the apache
environment. Another "good" reason for PERL is that I was able to
take a large portion of the code from example hook scripts - code for
parsing the results of svnlook, etc.

Does it make a difference? I suppose it imposes one more
requirement, PERL (with DBI support), but you'll find that in just
about any environment that also has PHP.

Thanks again for your feedback..

I have a working version of the .3 code here:
http://www.iduprey.c​om/kamikaze3

I plan to add RSS support and call it quits for .3

Packaging kamikaze

Author Guillaume Rousse <Guillaume dot Rousse at inria dot fr>
Full name Guillaume Rousse <Guillaume dot Rousse at inria dot fr>
Date 2006-03-19 13:24:42 PST
Message Hello.

I just packaged kamikaze 0.2 for mandriva. You might be interested by
the following patches:
- the fhs patch segregates files between configuration, browsable and
non-browsable files
- the db access fix fix a typo for db access

Also, you may consider cleaning up the archive:
- the various projects files are irrelevant for the user
- the various sql files may be merged into a single one, and the
dbcreate.sql dropped, as it enforce a fixed database name instead of
letting the user choose it
- the top-level directory versioning (0_2) is not consistant with the
software versioning (0.2)

What I don't understand, however, is why you did use perl for populating
database, and php for exploring it, instead of using a single language?
Attachments
Messages per page: