|
From: Scott H. <tal...@ne...> - 2010-08-12 04:13:52
|
On Aug 11, 2010, at 7:14 PM, cf...@im... wrote: > Incidentally and not that my view matters, it strikes me as odd to have > a policy of non-modification with respect to configuration files but to > be quite happy directing the output from MacPorts software to > system.log. I would personally be more bothered about keeping the > latter distinct than the former. (But then that's why I use the setup > described, I suppose.) The more that I think about this, and looking at some of the --with configure options, I am wondering... Please keep in mind, I am pretty new to the inner processes of source and make files, so if this is way out of line, please explain why it is a bad approach so I can learn from it. If I can set mandir, sbindir, docdir, initscriptdir etc, would it not also be beneficial to set syslog dir and syslog file, as well as perhaps the name of the facilities? Or is this purely a Mac OS X issue in that it was decided to use system.log for syslog instead of messages as I see on most other OS's? Thanks -- Scott (* For off-list contact, replace talklists@ with scott@ *) |