[MacPorts] #36560: Use hfsCompression

[MacPorts]

#36560: Use hfsCompression
--------------------------+----------------------
  Reporter:  mfeiri@…     |      Owner:  mfeiri@…
      Type:  enhancement  |     Status:  new
  Priority:  Normal       |  Milestone:
 Component:  base         |    Version:  2.1.99
Resolution:               |   Keywords:  haspatch
      Port:               |
--------------------------+----------------------
Changes (by ryandesign@…):

 * cc: rjvbertin@…, ryandesign@… (added)


Comment:

 Replying to [comment:21 rjvbertin@…]:
 > FYI, there *is* ZFS on OSX: www.o3x.org . While ZFS doesn't really
 support compression on a per-directory level, it does do fast (and less
 fast), transparent compression per mounted volume (dataset) ... and
 datasets can be made to mount wherever you want. So it would be perfectly
 straightforward to put all of MacPorts on a specific dataset, without the
 software even being aware of the fact. It'll be a little less
 straightforward if there is a dependency on HFS+ features, for example
 because you insist on Spotlight indexing or TM backups.
 > NB: ZFS's default compression algorithm actually tends to speed up I/O
 on spinning storage, as CPUs are usually faster than HDDs.

 I would say it is not MacPorts' job to suggest users use a third-party
 filesystem. We should assume MacPorts is installed on Apple's default
 filesystem and improve MacPorts to optimize that experience.

 > To come back to the patch: could this be made to apply to source code
 extraction too? Source trees can be huge and while users won't usually
 keep them around the same is probably not true for port developers. But
 maybe bsdtar has an option to "extract with compression"?

 I would not recommend that. Building from source is a CPU-bound activity;
 you don't want to slow down the CPU further with compression/decompression
 during that.

-- 
Ticket URL: <https://trac.macports.org/ticket/36560#comment:22>
MacPorts <https://www.macports.org/>
Ports system for OS X