On Sep 17, 2009, at 5:26 PM, Ryan Schmidt wrote:
I didn't realize there had been a specific decision not to do anything about configuration files in MacPorts base; I figured it was just something nobody had gotten to yet. There is an open ticket:
IIRC, the discussion in the past (which resulted in the decision to not do anything specific for conf files) included what to do if/when conf file formats change, or the sample files include new configuration options, etc.
While you can try to be 'really clever', it's easy to end up in a situation where you strangely mangle a user's conf file and they have to go in and fix things manually.
-- Daniel J. Luke +========================================================+ | *---------------- [email protected] ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+ _______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
