On Aug 12, 2013, at 11:29 AM, Clemens Lang <[email protected]> wrote: >> Personally, I would like to be able to globally disable it (with a >> conf setting) just to protect against the possibility that someone has >> it enabled for something that gets installed as a dependency that I >> don't actually want running [it would be cool if the implementation of >> the global 'off' switch for this automatically added a note (or at >> least a ui_msg) that says what would have been run, or what needs to >> be run to 'complete' the install]. > > That sounds like a good idea. Do you want to write a patch for this?
I figured that would be the response ;-) I can try to work something up, but I've been super-busy lately with $WORK so I'm not sure when I'll have time to hack on something (so if someone else wants to get something working before I have spare time, that's cool). I'll open a ticket with that description so I don't forget about it. -- 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] https://lists.macosforge.org/mailman/listinfo/macports-dev
