![]() An install is done using:Īll available Fink packages are listed here.Īll available DP packages are listed here. Installing applications in the terminal is easy. If you prefer a GUI package manager, you can try PortAuthority for DP or FinkCommander for Fink. You can find this application at /Applications/Utilities/Terminal. MacPorts manages the dependencies for you and makes it easy to later update or uninstall software too. Most people use a Terminal program to install the UNIX ports. MacPorts provides an easy way to install various open-source software products on macOS. This will allow you to use GUI apps and build applications from source which you will need at some point. ![]() You will also need to get X11 which you can find the X11User package (OS X CD - it's an optional install). Specifically, Homebrew has less packages than even Fink’s stable tree (not even close to MacPorts or Fink’s unstable tree). Younger means less packages, and perhaps a package you need is missing. If they aren't they are probably in DarwinPorts, so use DarwinPorts.īefore you install DarwinPorts or Fink, you should go to the Apple Developer Connection to register and download the newest version of XCode and Developer Tool. It’s a younger package tree than MacPorts or Fink. If most of your packages are in Fink, use Fink. So, if you install both the Fink and DarwinPorts versions of XFree86, funny things might happen. If 10.5 is not supported then the download page should be fixed. There is a catch as a few X11 applications (like XFree86), is installed /usr/X11R6. If you cannot upgrade you might try installing using MacPorts or Fink. DP has historically been a source/compile system, but since v1.2.1 you can also grab binaries.īy default, DarwinPorts installs in /opt/local, and should be able to coexist peacefully with Fink which installs in /sw. Due to it's heritage (OpenDarwin) chances are that most of the DarwinPorts ports will run without problem on Mac OS X Intel. The annoying part is that you're stuck with the versions of software that are in the package repository, which might not be all the applications you want to install.ĭarwinPorts (also known as MacPorts which mimics the FreeBSD ports architecture. ![]() That said, fink maintainers have been slow to move their packages over, so many applications will be of beta quality or may not compile. On Intel Macs, everything is currently built from source which is slow, but it seems to build everything fine so far. DarwinPorts is mostly written in Tcl, with some components written in C and has 3500 ports.įink is essentially a port of Debian's apt-get to OS X and it works pretty well even with the new Intel Macs. Fink is written in Perl and has 7000 ports. There is some overlap in ports and several people contribute to both the Fink and OpenDarwin projects. If other problems will be found, I'll update this post.Darwinports and Fink are complementary projects. No, not using the ppc arch is a bad way - I'm using a PPC So there is no straightforward way to find out what all you you’ve installed, especially if you’ve installed stuff by hand without using the App Store or Installer.app, or Homebrew or MacPorts or Fink or whatever. MacPorts is an application that allows Mac users to install easily. Maybe a little more time for the packager, but less time and size for the end users. Homebrew is a popular alternative for MacPorts, that is also open source. Universal (big big size) or divided by arch? In last case, we may need a makepkg's feature, from a single PKGBUILD obtain 2 (or 3) packages: ppc, x86 and x86_64. I'm unhappy with both: if we link to the apple libraries, we could break into these problems, but linking with our own will cause many missing dependencies when installing a single package (yes, there is pacman that handle this, but if I want a git installation I don't want 100 Mb of dependencies, otherwise I download the sources and compile it myself with 0 kb of dep). For handling this and don't hard-modify any PKGBUILD, IMHO we need to modify makepkg in a way that all installation will be prefixed with our default. ![]() For me, the best location isn't /usr or /usr/local, as explained here. Then, I discovered some point that needs to be discussed *before* implementation. The first thing is: Can be useful? How many are interested? So, instead of making packages for these project, I was thinking about a crazy idea: porting, and use, makepkg + pacman under OSX, with a public binary repository. In both cases, we have to compile all things, with a lot of dependencies every time. How many of us have used MacPorts to get all the tools we need under OSX? How many have used Fink (I hope a bit less, 'cause Fink is based on apt - and for me it is a pain! - )?
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |