For example, most ports are built with the compiler from Xcode.Īgain, poor word choice. > It will block writing files outside of directories specified in portsandbox.tcl, but using (reading and executing) system tools is allowed. > Its own versions of libraries, to be exact. I have ideas for ways to improve the ergonomics of the port command (and a willingness to write code to back it), but I'm not sure what the process is to get started on this. I "tested the waters" with a bug for a (IMO) usability improvement,, but didn't get much of response. > Development of the port command is relatively inactive (severe lack of manpower). I've been trying my best to help by updating whatever "port livecheck installed" gives me, provided the maintainer policy allows it :) I am curious about new ports, though: what is the policy on these? Should we aim to "mirror" packages that homebrew/core adds? Does MacPorts have any equivalent for Homebrew's Caskroom? > Yes, we need more contributors and committers to maintain the large collection of ports we have. Perhaps this is because I run on the bleeding edge (macOS Developer Seeds, macports-base/macports-ports built from ToT master)? Maybe I've triggered this by virtue of some configuration option I've set? Most of my packages seem to build from source. > Many packages in MacPorts (including LLVM) have pre-built binaries available from and its mirrors for macOS releases ranging from Mac OS X 10.5 to macOS 10.14. I haven't really gotten comfortable posting on macports-dev yet, so I hope you don't mind if I slip in a couple more questions in the development process my response ) As you may have noticed, I'm still learning my way around MacPorts (and writing, I guess). Yes, but we recommend users upgrading to a new major release of macOS reinstall MacPorts and all ports because things could still break. > The upside is that this approach is significantly more contained, which makes it easier to manage and more likely to continue working as macOS changes under it. For example, most ports are built with the compiler from Xcode. It will block writing files outside of directories specified in portsandbox.tcl, but using (reading and executing) system tools is allowed. > builds run in “sandboxes” under the macports user, where attempts to access files outside of the build directory–which includes system tools–are intercepted and blocked Its own versions of libraries, to be exact. > MacPorts will set up its own tools in isolation from those provided by the system We talked about this in a meeting last year, but it hasn't been implemented yet.ĭevelopment of the port command is relatively inactive (severe lack of manpower). > The lack of color, as well as somewhat more cluttered and less relevant output, makes it a bit less pleasant to work with. which automates updating checksums in the Portfile. We are also seeking for ways to improve our developer experience, e.g. Our ports are more often outdated than Homebrew because of this and our maintainer policy. Yes, we need more contributors and committers to maintain the large collection of ports we have. > MacPorts seems to be a bit lacking in manpower (which makes things takes slightly longer than I would have expected) "git" is not distributable because its license "gpl" conflicts with license "OpenSSL" of dependency "openssl". Port_binary_distributable.tcl describes the license conflicts. We don't provide official binaries for non-default variants or alternative prefix (the default is /opt/local) either, but organizations using MacPorts can set up private mirrors with custom ports and binaries. Many packages in MacPorts (including LLVM) have pre-built binaries available from and its mirrors for macOS releases ranging from Mac OS X 10.5 to macOS 10.14.īut if a port is considered not distributable because of its restrictive license or license conflicts with dependencies, binaries will not be uploaded to our official mirror so users have to build it from source. MacPorts almost always builds packages from source
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |