On Jan 10, 2015, at 1:53 PM, Ryan Schmidt <[email protected]> wrote:
> On Jan 10, 2015, at 12:05 PM, René J.V. Bertin wrote: > >> But how about moving the task to a background process? > > MacPorts does not currently have any background processes; adding one would > be a major change. This would also only be useful if there were something else MacPorts could be doing at the same time in the foreground. I think it would be confusing to add some sort of vacuum process that continued running after the main port(1) process exited. vq _______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
