On Saturday January 10 2015 17:14:48 Lawrence Velázquez wrote: > Do you expect a command-line foreground job to spawn background jobs that > continue after the foreground job has finished? I sure don't. And such > behavior would give a false impression that port(1) is finished, when it > actually is not.
Just a few examples that come to mind: zpool scrub smartctl -t long /dev/disk0 more appropriately akonadictl fsck akonadictl vacuum Those don't even post a message saying that the actual work they do happens in the background, only the manpage suggests to monitor the database server process to know when the fsck/vacuum'ing is finished. If MacPorts used a database requiring a server process it could well be that that final vacuum were done in the background too. R. _______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
