- translated from PRZECZYTAJ.TO using google translate

diff --git a/READ.ME b/READ.ME
new file mode 100644 (file)
index 0000000..70c0f7c
--- /dev/null
+++ b/READ.ME
@@ -0,0 +1,30 @@
+# vim:fileencoding=UTF-8
+# $ Revision: 1.4 $, $ Date: 2008/10/20 7:55:09 p.m. $ 
+
+Previous buildlogs engine was inefficient, especially for advanced search. This
+engine uses the sqlite3 database (php-pdo-sqlite) and is quite fast. 
+
+First you must initialize a database using a script migration.php. 
+This script requires php-program. Please run it again. Execution time 
+depends on the number of files and file system. This may take several minutes. 
+
+Then put the index.php, and powpld.png buildlogs.inc web server. 
+The script also requires php-gettext. 
+
+Each new buildlog (for new or old spec) should be 
+added to the database using the script addlog.php (using php-cli and php-pdo-sqlite). 
+Depending on whether the spec is new or not, the database will be updated 
+or added a new record. Addlog.php parameter for the absolute path 
+to file logos, 
+eg addlog.php /home/services/ftp/pub/pld-buildlogs/ac/i686/OK/kernel.bz2 
+
+Scripts index.php migration.php addlog.php and use the variable $database. 
+This variable should be identical in all three scripts. 
+Its current value is 'sqlite:/home/services/ftp/buildlogs.db'.
+It must be set to a value that the database file and directory in which it is situated 
+was writable by scripts and addlog.php migration.php and impossible to read! 
+index.php. 
+
+Configuration script is saved in a file buildlogs.inc. 
+After each change in this file, make sure that passes are correct 
+and rebuild the database by running migration.php.