Two User-Experience Problems
jfcaron at phas.ubc.ca
Thu Aug 20 13:37:57 PDT 2015
I replied just to Arno by accident, here is the same message for the list:
Oh! I saw a response about caffeinate, but I thought I had to install Caffeine to get it. Thanks for pointing it out. I will try making an alias for “sudo port upgrade” or “sudo port install” that prefixes it with caffeinate.
Regarding the buildmakejobs option that Daniel Luke pointed out: From what I read, this will make all build commands use the specific number that I put, if I don’t put 0, but some ports won’t build properly. I would like to leave the number of cores up to the system to determine, but cap it at some value.
I will try increasing the buildnicevalue instead of capping the cores. That should be equivalent from the user-experience perspective.
On Aug 20, 2015, at 12:51 , Arno Hautala <arno at alum.wpi.edu> wrote:
> On Thu, Aug 20, 2015 at 3:13 PM, Jean-François Caron
> <jfcaron at phas.ubc.ca> wrote:
>> 2) Since my OS is unusable during long builds, I walk away from the computer, but then it goes to sleep the build is paused. The current advice is to get a non-macports app called Caffeine to do some magic, or write a custom port wrapper to use pmset noidle before and after the port command. This should be an option in the MacPorts configuration somewhere, one shouldn’t have to resort to 3rd-party apps or scripting to get user-friendiness out of MacPorts.
> "caffeinate" has been included since Mountain Lion (10.8)
> arno s hautala /-| arno at alum.wpi.edu
> pgp b2c9d448
More information about the macports-users