> On Oct 3, 2015, at 2:44 PM, Clemens Lang <[email protected]> wrote: > > > > ----- On 3 Oct, 2015, at 23:33, Bradley Giesbrecht [email protected] wrote: > >> I understood that even with mpstatl installed it was still opt-in and the >> user >> had to make a config change to actually report. Is my understanding >> incorrect? > > mpstats uses startupitem.autoload to automatically start statistics reporting > after installation. It sends reports on a random weekday on the hour and two > minutes after you've installed it. > > See also: $> port notes mpstats: > Installing this port automatically enables weekly reporting of data to the > stats > server. Uninstall or deactivate this port if you want to stop providing > data to > MacPorts.
Thank you Clemens for the explantation. I read the Portfile and saw the startupitem.autoload which was a new control to me. My concern is that since there is consensus that we should not report without user intention that a mistake like mine where I did not know mpstat used startupitem.autoload that one cannot easily fix the issue for anyone who installed before the problem was fixed. They now have mpstat. I like that mpstat uses startupitem.autoload, I think it make the port simpler for those that want it. Is there a macports mechanism for declaring a port cannot be a dependent? — Brad _______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
