Now MacPorts will look for portfiles in the working copy and use Git instead of rsync to update your ports tree. The last line should look like this: rsync:///macports/release/tarballs/ports.tar Ĭhange it to point to the working copy you checked out: file:///opt/mports/macports-ports Then open /opt/local/etc/macports/nf in a text editor. This step is useful if you want to do port development.Ĭheck out the ports tree from git: $ cd /opt/mports (Optional) Configure MacPorts to use port information from Git configure to relocate MacPorts to another directory if needed.
#MACPORTS INSTALL PLPLOT WITH AQUATERM INSTALL#
These commands will build and install MacPorts to /opt/local. MacPorts uses autoconf and makefiles for installation. $ git checkout v2.6.2 # skip this if you want to use the development version This example will create /opt/mports/macports-base containing everything needed for MacPorts. Pick a location to store a working copy of the MacPorts code.įor this example, /opt/mports will be used, but you can put the source anywhere. The following notational conventions are used in the MacPorts Guide to distinguish between terminal input/output, file text, and other special text types. MacPorts base can be compiled on Linux (and possibly other POSIX-compatible systems) where it is mainly used to set up mirrors and generate support files for installations on macOS. In practice, installing ports only works on macOS. MacPorts is developed on macOS, though it is designed to be portable so it can work on other Unix-like systems, especially those descended from the Berkeley Software Distribution (BSD).
0 kommentar(er)
