[MacPorts] #61685: font-bh-lucidatypewriter-100dpi @1.0.3: extract failure: sandbox-exec: line 1: Error reading string
MacPorts
noreply at macports.org
Sat Nov 28 21:15:14 UTC 2020
#61685: font-bh-lucidatypewriter-100dpi @1.0.3: extract failure: sandbox-exec: line
1: Error reading string
----------------------------------------------+----------------------
Reporter: lawlist | Owner: jeremyhu
Type: defect | Status: assigned
Priority: Normal | Milestone:
Component: ports | Version: 2.6.4
Resolution: | Keywords:
Port: font-bh-lucidatypewriter-100dpi |
----------------------------------------------+----------------------
Comment (by lawlist):
Thank you Ryan for looking into this particular ticket. For approximately
the past 10+ years, I have been storing all of my important stuff in
`/Users/HOME/.0.data/`. I chose to use `.0.xxxx` and `0.xxxx` folder-
names because they alphabetize at the top when I use a variety of file
managers, and said naming convention is also used for stuff that I
consider important. I synchronize the entire contents of
`/Users/HOME/.0.data/` with multiple computers using `rsync`, and I
synchronize a select number of its subfolders with certain handheld
devices and also to a shared server up in cyberspace. For both
organization and synchronization considerations, as well as 10+ years of
doing what has been working well for my personal and business needs, I
would not be amenable to using another MacPorts destination at this time.
Is it possible for me to *manually* build `font-bh-lucidatypewriter-
100dpi` from source and install it to the
`/Users/HOME/.0.data/.0.emacs/.0.macports_2_6_4` directory using the
`--prefix` argument, and also tell MacPorts that the port/package has been
installed? I.e., I could do a manual install and then somehow make
Macports aware that the port/package has been installed.
--
Ticket URL: <https://trac.macports.org/ticket/61685#comment:3>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list