[MacPorts] #62376: texlive-bin tries to install stuff in system space even when macports is confihgured to put everything in home dir. [universal, Big Sur]

MacPorts noreply at macports.org
Wed Mar 3 15:34:40 UTC 2021


#62376: texlive-bin tries to install stuff in system space even when macports is
confihgured to put everything in home dir. [universal, Big Sur]
----------------------------+----------------------
  Reporter:  arthurcnorman  |      Owner:  drkp
      Type:  defect         |     Status:  assigned
  Priority:  Low            |  Milestone:
 Component:  ports          |    Version:
Resolution:                 |   Keywords:
      Port:  texlive-bin    |
----------------------------+----------------------

Comment (by arthurcnorman):

 Thank you very much. I tried flagging my issue as non-critical since I can
 just use "sudo" - I had not found the comments you refer to or understood
 all the background, but texlive is a big and complicated setup and a
 desire to be able to flip between different versions of it and potential
 other TeX implementations is good.
 I do not see what I am doing as anything other than a temporary hack, but
 it has given me enough to be able to build a universal version of Reduce.
 As to raising issues elsewhere, I had contributed comments on issue 61545
 and the proper MacPorts people had clearly been making good progress - but
 I was still finfing that the installation of xorg-libx11 was set to
 include python38 which doe snot yet build for arm64+x86_64, and many
 things depend on ossp-uuid where my attempts to get a patch that O could
 propose had stalled. So this was impatiance on my part and I really look
 forward to when "everything" just builds with +universal.

 While here can I ask about the plans for building in +universal mode on
 Big Sur but an INtel CPU. Sort of obviously many more ports will not build
 the arm64 variants there where the build wishes to run things in the
 target architecture. I can happily generate trak entries for the cases I
 find but only want to clutter things up if you view that sort of cross
 build as supportable and reasonable. I would start with ossp-uuid, libpng
 and of course python38 and eveything that depends on it... but it only
 make sense for me to do that it it will be useful!

-- 
Ticket URL: <https://trac.macports.org/ticket/62376#comment:3>
MacPorts <https://www.macports.org/>
Ports system for macOS


More information about the macports-tickets mailing list