Error Port Not Found Macports
Contents |
Development4.1. Portfile Introduction4.2. Creating a Portfile4.3. Example Portfiles4.4. Port Variants4.5. Patch Files4.6. Local Portfile Repositories4.7. Portfile macports el capitan Best Practices4.8. MacPorts' buildbot5. Portfile Reference5.1. Global Keywords5.2. Global macports gcc Variables5.3. Port Phases5.4. Dependencies5.5. Variants5.6. Tcl Extensions amp; Useful Tcl Commands5.7. StartupItems5.8. Livecheck macports clean / Distcheck5.9. PortGroups6. MacPorts Internals6.1. File Hierarchy6.2. Configuration Files6.3. Port Images6.4. APIs and Libs6.5. The MacPorts Registry7. MacPorts Project7.1. Using Trac
Macports Uninstall
for Tickets7.2. Contributing to MacPorts7.3. Port Update Policies7.4. MacPorts Membership7.5. The PortMgr Team8. MacPorts Guide TermsGlossary2.2. Install MacPortsPrev Chapter 2. Installing MacPorts Next Single Page Chunked 2.2. Install MacPortsIf you are using OS X, you should install MacPorts using the OS X package installer unless you do not macports alternative wish to install it to /opt/local/, the default MacPorts location, or if you wish to install a pre-release version of MacPorts base. However, if you wish to install multiple copies of MacPorts or install MacPorts on another OS platform, you must install MacPorts from the source code.NoteThough a distinction is made between pre-release and release versions of MacPorts base, the ports collection supports no such distinction or versioning. The selfupdate command installs the latest port revisions from Subversion (at a slight delay), and updates MacPorts base to the latest released version.2.2.1. OS X Package InstallThe OS X package installer automatically installs MacPorts, sets the shell environment, and runs a selfupdate operation to update the ports tree and MacPorts base with the latest release.Download the latest MacPorts-2.3.4-Macports Vs Homebrew Portfile Reference5.1. Global Keywords5.2. Global Variables5.3. Port Phases5.4. Dependencies5.5. Variants5.6. Tcl Extensions & Useful Tcl Commands5.7. StartupItems5.8. Livecheck / Distcheck5.9. PortGroups6. MacPorts Internals6.1. File Hierarchy6.2. Configuration Files6.3. Port Images6.4. APIs and Libs6.5. The MacPorts Registry7. MacPorts Project7.1. Using Trac for Tickets7.2. Contributing to MacPorts7.3. https://guide.macports.org/chunked/installing.macports.html Port Update Policies7.4. MacPorts Membership7.5. The PortMgr Team8. MacPorts Guide TermsGlossaryChapter 1. IntroductionMacPorts is an easy to use system for compiling, installing, and managing open source software. MacPorts may be conceptually divided into two main parts: the infrastructure, known as MacPorts base, and the set of available ports. A MacPorts port is a set of specifications contained in https://guide.macports.org/ a Portfile that defines an application, its characteristics, and any files or special instructions required to install it. This allows you to use a single command to tell MacPorts to automatically download, compile, and install applications and libraries. But using MacPorts to manage your open source software provides several other significant advantages. For example, MacPorts:Installs automatically any required support software, known as dependencies, for a given port.Provides for uninstalls and upgrades for installed ports.Confines ported software to a private “sandbox” that keeps it from intermingling with your operating system and its vendor-supplied software to prevent them from becoming corrupted.Allows you to create pre-compiled binary installers of ported applications to quickly install software on remote computers without compiling from source code.MacPorts is developed on OS X, 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). In practice, installing ports only works on OS X. MacPorts base can be compiled on Lin here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers http://stackoverflow.com/questions/28259926/error-port-gnuplot-not-found or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Error : Port gnuplot not found up vote 0 down vote favorite I have just installed macports as per the instruction given on their website. But as i type sudo port install gnuplot error port i get an error Error: Port gnuplot not found also for self update i get Error: Error synchronizing MacPorts sources: command execution failed Please run `port -v selfupdate' for details. Error: /opt/local/bin/port: port selfupdate failed: Error synchronizing MacPorts sources: command execution failed It is same for any software i am trying to download using macport. How to solve this issue? Is it because my college firewall is blocking downloads using macport? Which port do macport use to download? And also error port not if they are blocking it how come linux users can download using yum, apt-get etc macports share|improve this question edited Feb 1 '15 at 5:52 Andrew Savinykh 11.2k64373 asked Feb 1 '15 at 5:50 ruskin23 263 add a comment| 1 Answer 1 active oldest votes up vote 0 down vote You can run sudo port -d selfupdate to see why the update fails. I'm assuming it's because your local network blocks outbound access to port 873 (rsync), which MacPorts uses for updating. You should really ask your network administrator to allow outbound rsync – there's really no danger whatsoever associated with it. To my knowledge, MacPorts is the only package manager, which uses the rsync protocol, so that explains why yum, apt-get and others work fine. The synchronization failure also explains why the gnuplot port doesn't exist for you. MacPorts needs a file that tells it how to get and build gnuplot, which it downloads using rsync. If that never worked for you, you don't have the file and hence MacPorts assumes there is no gnuplot port. If your network administrators refuse to open the rsync port (for whatever reason), there's an FAQ entry to work around that, as well: http://trac.macports.org/wiki/FAQ#selfupdatefails. share|improve this answer answered Feb 1 '15 at 12:13 neverpanic 1,866717 add a comment| Your Answer draft saved draft discarded Sign up or log in Sign up using Google Sign up using Facebook Sign uMacports Update