[MacPorts] #32261: Allow building on a RAM disk or other secondary disk
MacPorts
noreply at macports.org
Sat Jul 9 16:06:56 UTC 2022
#32261: Allow building on a RAM disk or other secondary disk
--------------------------+--------------------------------
Reporter: skolah@… | Owner: macports-tickets@…
Type: enhancement | Status: new
Priority: Normal | Milestone:
Component: base | Version: 2.0.3
Resolution: | Keywords:
Port: |
--------------------------+--------------------------------
Comment (by mascguy):
Replying to [comment:1 ryandesign]:
> [http://lists.macosforge.org/pipermail/macports-
users/2011-November/026093.html This message from Gregory Seidman] shows
how you can do that.
>
> I don't think we need any changes to MacPorts base for this. However it
would be great if someone wanted to turn Greg's post into a wiki/howto
page.
It would still be highly-desirable if one could specify a path, via a
formal MacPorts config property like `build_dir`. (Just as we currently
support `ccache_dir`.)
And given that macOS doesn't support the ability to create mount-points to
arbitrary target paths, that scenario requires the use of a FUSE
filesystem like `bindfs`.
In any event, here's my use-case: Presently I have a single NVMe SSD,
which I use for non-critical data like CCache. And MacPorts is setup to
utilize the latter, across my various physical macOS installations.
Here's how that volume is setup, to illustrate:
{{{
/Volumes/Mac-MacPorts-Common/MacPorts/CCache/CCache-10.13/.ccache/
/Volumes/Mac-MacPorts-Common/MacPorts/CCache/CCache-10.14/.ccache/
/Volumes/Mac-MacPorts-Common/MacPorts/CCache/CCache-10.15/.ccache/
}}}
Each MacPorts installation is configured to use the appropriate CCache
repo, which matches the macOS version.
I'd now like to setup something similar, for the MacPorts build dirs. So
the setup might look like the following:
{{{
/Volumes/Mac-MacPorts-Common/MacPorts/Build/Build-10.13/build
/Volumes/Mac-MacPorts-Common/MacPorts/Build/Build-10.14/build
/Volumes/Mac-MacPorts-Common/MacPorts/Build/Build-10.15/build
}}}
If a config property like `build_dir` existed, this would be a no-brainer,
with nothing else required.
Thoughts?
--
Ticket URL: <https://trac.macports.org/ticket/32261#comment:5>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list