Marcin Kasperski a écrit : > It should not be necessary, if somebody issues just > ./configure > it is equivalent to > ./configure BINDIR=/usr/local/bin SHAREDIR=/usr/local/share/scid > (both those defaults are set in configure file and seem reasonable) > > Maybe the fallback could help if one runs scid in the compilation dir. > This is always my case : I always use Scid from the compilation dir, and maybe others do the same (I understand people that are reluctant to issue a make install as root). > But usually even then scid will find the results of possible earlier > installation... > > Testing whether books or bases are present makes sense, but > I would split it into the two tests (so the message specifies what > exactly is not found) and add directory to the message (so one > knows where scid wanted to find them)
That is right, I will improve feedback to the user. Pascal ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Scid-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/scid-users
