[MacPorts] #37157: why no provide multicore build by default? =(

MacPorts noreply at macports.org
Wed Nov 28 07:28:52 PST 2012


#37157: why no provide multicore build by default? =(
--------------------------+--------------------------------
  Reporter:  jkuhnert@…   |      Owner:  macports-tickets@…
      Type:  enhancement  |     Status:  closed
  Priority:  Normal       |  Milestone:
 Component:  base         |    Version:  2.1.2
Resolution:  invalid      |   Keywords:
      Port:               |
--------------------------+--------------------------------

Comment (by jkuhnert@…):

 I could be using selective memory here but I'm almost certain that value
 was set to 1 for me. Maybe I changed it in the past but I'm fairly anal
 retentive and think I'd remember something like that? I've also gone
 through multiple macports core upgrades so maybe this was a lingering
 artifact of a previous version.

 It's one of those two, if it's the latter and not me wasting your time
 again perhaps a simple one-liner warning message could be output when
 doing any build by having it always detect number of cores if value not 0.
 I'm sure there's some fraction of users that would find a reason to hate
 this option as well but for people who somehow ended up with the non-l33t
 default it sure would be nice to know there's a way to make it faster. I
 only share because I love macports so much, but clearly not enough to
 help. ;)

-- 
Ticket URL: <https://trac.macports.org/ticket/37157#comment:2>
MacPorts <http://www.macports.org/>
Ports system for Mac OS


More information about the macports-tickets mailing list