![]() Getting startedįor information on installing MacPorts please see the installation section of this site andĮxplore the myriad of download options we provide and our base system requirements. There are thousands of ports in our tree, distributed among different categories, and more are being added on a regular basis. (including macOS Ventura v13 on both Intel and Apple Silicon). “unstable” branches, targeting mainly macOS Catalina v10.15 and later We provide a single software tree that attempts to track the latest release of every software title (port) we distribute, That greatly simplify the task of compiling and installing open-source software on your Mac. To that end we provide the command-line driven MacPorts software package under a 3-Clause BSD License, and through it easy access to thousands of ports Others may need updates which gets more complicated.Īlso, this only covers basic port updates, need to also cover changing versions of the various groupcode-based ports.The MacPorts Project is an open-source community initiative to design an easy-to-use system for compiling, installing,Īnd upgrading either command-line, X11 or Aqua based open-source software on the Mac One thing to add is about patches, some may no longer be needed (they're irrelevant with the new version, they've been integrated upstream, etc), so should be removed. diff as a file to be attached to the new ticket.ĭo a little clean up so extra files aren't left around: Second, to make it easier for the maintainer you should attach a diff against the Portfile to the new ticket, so generate a diff by running:ĭiff -u Portfile.orig Portfile | sudo tee. If you decide to file a Trac ticket instead: First, please don't forget to add the port maintainer's email addresses in CC. Your request will get faster attention and it is much easier for the MacPorts team to process it that way. Since it succeeded, file a pull request on Github or file a ticket with Trac to upgrade the port to the new version.įiling a pull request on Github is considered superior. Otherwise, the port will be installed with the latest version specified. If it doesn't succeed, that goes beyond the scope of this document. ![]() Use the debug flag again so that, in case something bad happens, the error message will be seen. Now that the correct checksum has been specified, you can install the new version with: Similarly, if the Portfile has a livecheck section which uses livecheck.check md5, run:Īnd update the Portfile's livecheck.md5 key with the new md5sum. Sha256 fb3a1109cbe888fb0920bf13e910265d8be17048e17555ee323fa9cf85cdd9f2 \Ĭopy this section (all three lines), use sudo port edit again, and change the checksum lines to be what you just copied. This will fail and since the debug (-d) flag was used, specify the checksums from the new file (among other lines):Ĭhecksums rmd160 1799d0d28adaaae58063d387b4d6f36d4aedadcf \ This will fetch the new version you've specified then run a checksum against the downloaded file. ![]() Now fetch and run the checksum phase (which will fail, since it hasn't been updated for the new version) by running: Step 4: Fetching and updating the checksums Updated versions should start with revision 0 (which is the default when revision isn't present). For example, if the new version is 1.5, it should simply look like:Īnd if found reset it to zero. Update the version given on that line (1.4.1 in this example) to the newly-desired version, then save the Portfile. Once the Portfile has been opened, find the line which starts with version: This will open nano to edit the Portfile for the given port. Since you're already in the directory containing the Portfile, you can also open it directly from here, but port edit always works.Īs of MacPorts 1.7, you can also choose your editor from the command line directly instead of the environment variables: To edit the Portfile for the given port (this will open it in whatever editor you have defined via the VISUAL or EDITOR environment variables, or vi if not defined). Updating the port Step 1: Getting into the port directory and keeping a copy of the originalįirst, cd into the port's directory (which contains the Portfile) by running: The Portfile for a port can be updated locally to allow you to upgrade it now, without waiting for an official update from the maintainer.Īnytime you see in this document, replace with the actual name of the port in which you are interested, it is only a placeholder here. ![]() When other ports are updated this can cause issues when the newer version of a port is needed for compatibility. Sometimes ports will fall behind the currently-available version. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |