1-- Changes in 0.8.1 ----------------------------------------------------------- 2 3- The restrict_* configuration options now accept wildcards (? and *). 4 5 6-- Changes in 0.8 ------------------------------------------------------------- 7 8- SQLite is now supported as a database backend. However, portscout must be 9 run in non-forking mode when using SQLite. This may or may not change in the 10 future, but as a consequence, it is recommended that SQLite only be used for 11 light workloads. 12 13 To put portscout into non-forking mode, be sure to set 14 15 num children = 0 16 17 in portscout.conf. 18 19- CVSup logs are no longer required; the 'rebuild' method employed by 20 portscout has now been replaced with the new 'mtime' option; this is cleaner 21 and simpler, and requires no external files beyond a working ports tree. 22 23- Master site data are no longer cached, nor even written to disk. The 24 cache_ms_data and ms_data_dir options are now deprecated. The directory used 25 for the latter can safely be deleted. 26 27- An INDEX file is no longer required to run portscout, unless a 28 restrict_maintainer constraint is in force. In this case, use of INDEX can 29 be switched off using indexfile_enable, but rebuilding will be as slow as 30 a full build. 31 32- It was previously suggested that 'build' could be used in place of 'rebuild' 33 in case CVSup logs could not be provided to portscout. This is no longer the 34 case. Be sure to always use 'rebuild' and not 'build', except for initial 35 population of the database. 36 37- Static portconfig entries (as provided in initdata.sql) are now deprecated. 38 These must be set via the PORTSCOUT variable in ports. Static entries can 39 still be used, but will be lost if the port moves. 40