#56435 closed enhancement (fixed)
selfupdate should use parallel build
Reported by: | ryandesign (Ryan Carsten Schmidt) | Owned by: | jmroot (Joshua Root) |
---|---|---|---|
Priority: | Normal | Milestone: | MacPorts 2.8.0 |
Component: | base | Version: | 2.4.99 |
Keywords: | Cc: | ||
Port: |
Description
Is there a good reason why selfupdate doesn't build MacPorts base in parallel?
Change History (4)
comment:1 Changed 7 years ago by ryandesign (Ryan Carsten Schmidt)
comment:2 Changed 2 years ago by jmroot (Joshua Root)
Owner: | set to jmroot |
---|---|
Resolution: | → fixed |
Status: | new → closed |
comment:3 Changed 2 years ago by jmroot (Joshua Root)
Milestone: | → MacPorts Future |
---|
comment:4 Changed 2 years ago by jmroot (Joshua Root)
Milestone: | MacPorts Future → MacPorts 2.8.0 |
---|
Note: See
TracTickets for help on using
tickets.
Assuming there isn't a good reason, we should make it build in parallel. Base has grown over the years, with bundled copies of other libraries, and now that Macs have more processor cores, parallel building can save a bit of time.
How should it be done? I hoped I could reuse the existing functionality in
portbuild::build_getjobsarg
but I assume most of that procedure (except the parts that checkuse_parallel_build
andbuild.cmd
), and all ofportbuild::build_getjobs
, should be moved into a file that's not meant to be specific to the port build phase. If so, where should it go? Intomacports::
? The tests will then need to be updated too, since they test those procedures.