Opened 9 years ago
Last modified 8 years ago
#48423 new enhancement
Replace bzip2 and gzip with pbzip2 and pigz system wide?
| Reported by: | andre.david@… | Owned by: | macports-tickets@… |
|---|---|---|---|
| Priority: | Low | Milestone: | |
| Component: | base | Version: | |
| Keywords: | Cc: | ||
| Port: |
Description
I just went through a rather lost installation that stalled compressing something with bzip2, making the fans go crazy while only using one core.
I was wondering if both pbzip2 and pigz could have an option to override the bzip2 and gzip or if there is a better way for me to transparently get pbzip2 to run when bzip2 is called.
Change History (6)
comment:1 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)
| Component: | ports → base |
|---|---|
| Type: | request → enhancement |
comment:2 Changed 9 years ago by mf2k (Frank Schima)
| Port: | pbzip2 pigz removed |
|---|
comment:3 Changed 8 years ago by andre.david@…
For some reason I have pbzip2 but port still uses bzip2.
Any suggestion on how to go about debugging why this is the case?
comment:4 follow-up: 5 Changed 8 years ago by neverpanic (Clemens Lang)
r121711 is not in a released version of MacPorts yet. Only the development version has it.
comment:5 Changed 8 years ago by andre.david@…
comment:6 Changed 8 years ago by neverpanic (Clemens Lang)
Since this is an enhancement, it will get released with the next non-patch version of MacPorts we release, which would be MacPorts 2.4.0. You can help out by installing a development version of MacPorts, testing and reporting any bugs you find. See https://guide.macports.org/#installing.macports.subversion for instructions on installing a development version.
Note that while you can upgrade your current installation to a development copy, you can not downgrade due to changes we do to the database on upgrade. If you do not want to switch your MacPorts installation to the development version, install the development copy into a separate prefix (pass --prefix=$value to ./configure).
Additionally, we may want to discuss offering the possibility to create symlinks from $prefix/bin/bzip2 to lbzip2 or pbzip2 and the same for gzip/pigz. This could be done using a bzip2_select and gzip_select port.
MacPorts will automatically use lbzip2 or pbzip2 if available instead of bzip2; this was added in r121711. I don't think anything has been done regarding other compression methods. bz2 was probably prioritized because it is the format we use for our binary archives.