]> git.pld-linux.org Git - projects/buildlogs.git/blame - READ.ME
Catch errors like: make[2]: *** No rule to make target '/usr/lib64/libhdf5.so.1.8...
[projects/buildlogs.git] / READ.ME
CommitLineData
e124efb4
ER
1# vim:fileencoding=UTF-8
2# $ Revision: 1.4 $, $ Date: 2008/10/20 7:55:09 p.m. $
3
4Previous buildlogs engine was inefficient, especially for advanced search. This
5engine uses the sqlite3 database (php-pdo-sqlite) and is quite fast.
6
7First you must initialize a database using a script migration.php.
8This script requires php-program. Please run it again. Execution time
9depends on the number of files and file system. This may take several minutes.
10
11Then put the index.php, and powpld.png buildlogs.inc web server.
12The script also requires php-gettext.
13
14Each new buildlog (for new or old spec) should be
15added to the database using the script addlog.php (using php-cli and php-pdo-sqlite).
16Depending on whether the spec is new or not, the database will be updated
17or added a new record. Addlog.php parameter for the absolute path
18to file logos,
19eg addlog.php /home/services/ftp/pub/pld-buildlogs/ac/i686/OK/kernel.bz2
20
21Scripts index.php migration.php addlog.php and use the variable $database.
22This variable should be identical in all three scripts.
23Its current value is 'sqlite:/home/services/ftp/buildlogs.db'.
24It must be set to a value that the database file and directory in which it is situated
25was writable by scripts and addlog.php migration.php and impossible to read!
26index.php.
27
28Configuration script is saved in a file buildlogs.inc.
29After each change in this file, make sure that passes are correct
30and rebuild the database by running migration.php.
This page took 0.225377 seconds and 4 git commands to generate.