| Fink & Apple's X11 |
|
/ Fink and Panther / - Fink and Panther FAQ - Contents fink selfupdate-rsync How do I get Fink to realize I'm running Panther? Fink xfree86 4.3.0-14 and Panther Upgrading your previous Fink installation Which packages have been updated to work with 10.3? Short 'fink list' on Panther w/ Fink 0.6.0 "no such file or directory" errors Which trees are updated by the rsync update method? Fink keep asking to install xfree86? On Panther but fink.conf says ""Distribution: 10.2" To remove Fink xfree86 and install Apple's X11 system-xfree86- "The State of Fink" gcc2 [virtual package representing the gcc2 compiler] Install dlcompat-shlibs if you use the bindist Problem with the qt3 package in the 10.3 bindist How can I grab the source to a package? Tried to install fink-0.5.3-full on Panther Using Fink to install KDE on Panther Installing Fink Binary packages in Panther Updating Fink emacs21-xaw3d in Panther Panther default open source packages and Fink bus error after fileutils update compiling qt3-3.2.2-1 fails a root directory /sw exists The "trailing slash" or "mv" bug /sw/bin/pathsetup.command; exit /sw/fink/10.2 - /sw/fink/10.2-gcc3.3 fink selfupdate-rsync Switching to the Rsync Upgrade Method Since version 0.14.0 , the fink package manager offers a new update method, upgrading via rsync, as an alternative to the CVS upgrade method. After you installed the latest fink package manager, running the command: 'fink selfupdate-rsync' will switch you to the new method. Once you have switched, you can do subsequent updates with the simple command: 'fink selfupdate' `fink selfupdate' is the only documented method of updating package descriptions. It is not advised to switch frequently between update methods; you should pick one method and stick to it. You can switch between rsync and cvs update methods, but it is not recommended, as it's not sure whether the anonymous 'cvs update method' will remain an option for fink users. It is possible that the ability for users to do 'anonymous cvs selfupdate's' will be removed from fink as soon as Fink gets more 'rsync' mirrors. To change the selfupdate method edit the: "SelfUpdateMethod" field in the /sw/etc/fink.conf file. SelfUpdateMethod can be set to one of "cvs" " rsync " or "point" . Changes to this field are recognized the next time fink selfupdate is run, and the method listed in the configuration file will be used. For more info check 'man fink.conf'. -Firewall problem - Are you behind a firewall? Does it allow rsync connections to pass through? rsync uses port 873. You may also use a web proxy, if it allows CONNECT on port 873. See the rsync man page, and look for RSYNC_PROXY. -The new rsync method only updates the trees which are mentioned in your fink.conf file, so a user who does a selfupdate with only 'stable' enabled will not get new unstable package descriptions. -All CVS directories under /sw/fink will be removed when you run the rsync update method. How do I get Fink to realize I'm running Panther? Run: sudo /sw/lib/fink/postinstall.pl Fink xfree86 4.3.0-14 and Panther 4.3.0 is broken is broken on Panther. It is suggested to use Apple's X11 instead, or you can install fink's package xfree86 4.3.99. It should work fine on Panther. Upgrading your previous Fink installation If you installed Panther with the 'archive and install' method, and then installed Apple's X11 1.0 and the X11 SDK, be sure to install XCode from the XCode disk before upgrading Fink. Then, running: fink selfupdate should perform the upgrade for you. The latest version of the fink package manager will automatically detect which version of OS X and which version of gcc you have installed, and will adjust itself accordingly. Which packages have been updated to work with 10.3? Run 'fink list' on 10.3 Short 'fink list' on Panther w/ Fink 0.6.0 You need to do a "fink selfupdate" and choose a method other than the point release (preferably rsync) and get the latest package descriptions. (you may need to run "fink index" afterwards) "no such file or directory" errors The "no such file or directory" errors typically mean that something failed to build earlier on. Check further back in your output for a different error. Which trees are updated by the rsync update method? The rsync update method only updates those trees which are enabled in fink.conf, add unstable/main and unstable/crypto to your Trees: line in fink.conf and fink selfupdate will update them. Fink keep asking to install xfree86? If after installing Apple's X11, Fink keep asking to install xfree86, you need to: Install the X11 SDK, which is on the Xcode CD (double click the X11SDK.pkg), and is not installed by default. If you have Apple's X11 installed, you should never answer "y" when fink propose to install xfree86-* packages. If you do answer 'y' it could happen that you will end up with a bunch of half-installed packages that may be hard to get rid of. Also note that you do not need to install system-xfree86 anymore, fink is capable of figuring out your X11 version automatically in cases where you would have installed system-xfree86 previously. If you still have an old system-xfree86 package installed, run the following commands:
On Panther but fink.conf says ""Distribution: 10.2" Standard upgrade to Panther; Apple's X11, Xcode and X11 SDK installed. However, in fink.conf still have one line saying "Distribution: 10.2". Should it not be 10.3? If you run 'fink reinstall fink' this should get corrected to 10.3. To remove Fink xfree86 and install Apple's X11
Then install Apple's X11 1.0 from the Panther CD including Xcode and the X11 SDK from the XCode CD. You don't need to install system-xfree86 anymore. It's automatically generated if fink detects a valid x11 install. system-xfree86- With recent versions of fink (the program), you don't need any system-xfree86-* packages. Force-remove any system-xfree86 packages you have installed. If you have no system-xfree86 installed, fink automatically provides a system-xfree86 package that knows exactly what your X11 is capable of. To check, run: 'fink-virtual-pkgs' In the resulting list, you should see the lines:
If you don't see this information: - you either have an incomplete installation of X11 (missing something from the SDK, for example). - or did not remove the "real" system-xfree86 packages. Only when they are gone can the virtual package show up. "The State of Fink" This is important information for all fink-users, please read carefully and follow what's necessary to do for your system. The following was posted by Benjamin Reed (Fink Project Leader) at the fink-users list, on Oct 24th: The State of Fink "In some parts of the world, Panther is already out, so I wanted to give an update on where things are. A more formal announcement will come when we're ready for a "real" release. How This Will Work First of all, unlike the transition from 10.1 -> 10.2, we will continue to support the previous Mac OS X release. It may not be updated as quickly as the 10.3 tree, but we now at least have the resources in place to make it reasonable to support both. It would be nice to have volunteers from the community to help "backport" 10.3 changes, but that is something that will probably have to be worked out later. If you're interested, drop a line to fink-core@lists.sourceforge.net. The Transition to GCC 3.3 HOWEVER, to ease keeping things in sync between 10.2 and 10.3, our continued support for 10.2 will *only* be if you are using the gcc 3.3 update, since the differences between gcc3.1 and 3.3 are reasonably large as far as how porting happens. If you've been following the fink-devel list, you know that for the past few months we've been working on a tree dubbed "10.2-gcc3.3", which currently contains most of the packages in the 10.2 tree, updated to work with the new compiler. Even now more packages are getting moved over each day, and tools have now been written to make it easier to track changes between the different development trees. The 10.2-gcc3.3 tree is perfectly usable right now, although a little incomplete in unstable. David R. Morrison is working incredibly hard to finish putting together the first binary distribution for 10.2-gcc3.3, and it is expected to be coming any day now. The Transition to Panther The initial target for Panther users will be for you to use the 10.2-gcc3.3 binary distribution. This tree is binary-compatible with Panther and should provide a smooth upgrade path to the "real" 10.3 tree. The 10.3 tree is currently based on a subset of 10.2-gcc3.3, and is, like it's predecessor, continuously getting updated and is getting closer to parity with the other trees as time goes on. There's still plenty of work to do, but almost all of stable is there, and ready, and developers are diligently getting packages moved over to the unstable tree. What You Can Do Please help us test the 10.2-gcc3.3 and 10.3 trees. 10.2: If you're running 10.2, install the December developer tools if you haven't already, and then install the August updater. You can get them both at the Apple Developer Connection http://developer.apple.com/ It does require registration, but is free. 10.3: If you're already running 10.3, be warned that if you installed fink's X11 package (instead of a system-xfree86 package), you may need to force-remove them, and then re-install Apple's X11 (make sure you also install the X11 SDK from the developer tools!) Everyone: Download the 0.15.1 beta of fink here: Download 0.15.1 beta of fink ...and follow the instructions for the rsync upgrade (which are good general instructions for upgrading your fink package manager to the beta): http://fink.sourceforge.net/download/rsync-upgrade.php The beta will set you up for 10.2-gcc3.3 or 10.3, depending on what OS version you are running. *Please* keep in mind that you shouldn't use apt-get or dselect to install things until we have a binary distribution (or if you do, make sure you do "fink update-all" afterwards so that any 10.2-gcc3.3 fixes or upgrades get built and installed). Once the 10.2-gcc3.3 bindist is ready, we will make an announcement and it will be safe to use binary tools again. Also keep in mind that for now, 10.2-gcc3.3 and 10.3 are still considered "beta". Expect the occasional problem. Generally, things are working pretty well, though. We'll let you know as soon as something official is available". gcc2 [virtual package representing the gcc2 compiler] In Panther: Fink automatically creates it internally, if you installed the optional gcc 2.95 along with gcc 3.1 and 3.3 when you installed Xcode. You don't need to remove it. It's just a convenient placeholder to make sure packages depend on it properly, now that gcc2 is optional in panther. It's one of the new "virtual" packages fink is capable of providing automatically based on what is on your system. Install dlcompat-shlibs if you use the bindist If you are using the 0.6.1 binary distribution on Panther, install the dlcompat-shlibs package: sudo apt-get install dlcompat-shlibs At the moment, the dlcompat package will fail to trigger the installation of dlcompat-shlibs as a dependancy. Problem with the qt3 package in the 10.3 bindist The qt3 packages in the 10.3 bindist will have to be replaced. Posted by Benjamin Reed at the fink-devel lists: "The problem is that XFree86 was disabling a flag that provides backwards-compatible symbols for freetype, so a libfreetype from XFree86 4.2 (including Apple's X11) has some symbols that a libfreetype from XFree86 4.3 doesn't. I've notified the XFree86 team about this and it's already fixed in CVS, a future XFree86 4.3.1 release or the upcoming 4.4 release will both solve the problem. In the meantime, qt3 needs to be rebuilt". How can I grab the source to a package? 'fink fetch some_package' The source should wind up in /sw/src The patches live in your /sw/fink/dists/ directory. Tried to install fink-0.5.3-full on Panther You need to bootstrap *from* fink-0.6.0-full, not 0.5.3. Using Fink to install KDE on Panther Install Apple's X11 1.0 from the Panther CD, Xcode and the X11 SDK from the Xcode CD. Install Fink from: Fink Binary Installer 0.6.1 or Fink Source Release 0.6.1 Then, to install all of the official KDE packages with Fink, install: 'bundle-kde' or 'bundle-kde-ssl' To install binaries, you can use apt-get: sudo apt-get update sudo apt-get install bundle-kde From source: fink selfupdate fink install bundle-kde If you are using Apple's X11 but want to use the KDE window manager, create a file called ".xinitrc" in your home directory, with the following lines:
-If you plan on running in rootless mode, you will likely want to disable desktop icons, or else the root window desktop will cover up your Aqua destkop. You can do this by starting the KDE control center, expanding the "Desktop" list, click "Behavior", and uncheck the "Enable icons on desktop" checkbox. -If you have problems to access the KDE control center in Apple's X11, choose minimize from the Apple's X11 Window menu after KDE has launched, the KDE desktop shrinks to the Dock and and you will be able to access KDE windows and menus with the mouse or keyboard. -If you try to run KDE apps after you upgraded to Panther and Fink 0.6.1 and get the following error messages:
Your best bet will be to recompile qt3. Run: fink rebuild qt3 It takes about 3 hours, you will need the Xcode tools installed, including the X11 SDK. Installing Fink Binary packages in Panther 1- Install Apple's X11 from the X11.pkg on Panther CD 3. 2- Install Xcode and the "X11 SDK" from the Xcode CD. 2- Install Fink: Download the installer disk image from: Fink 0.6.1 Binary Installer - 18 MB Don't Use dselect: The binary release uses binary packages. It comes with a graphical installer package for first-time installation and a package browser and selection app (dselect). But, dselect is broken in Panther, and if you try to install via dselect, Fink will indicate that it needs X11, and will offer xfree86-base and system-xtools as options, and it could also exhibit a problem where all users get deleted from the netinfo database, and you become unable to log in, in the case you have bootstrapped or installed Fink 0.5.3 or Fink 0.6.0 on Mac OS X 10.3 . For installing binary packages in Panther, you can use: the command apt-get or FinkCommander Important before you start installing packages: Check that the file /sw/etc/apt/sources.list has 10.3 in the deb lines:
Then run: fink scanpackages (only needed the first time you do this) --------------------------- - For the binary packages to become available in FinkCommander: Run "Update" followed by "Dist-Upgrade" (both in the Binary menu) Or Run: Binary:Update descriptions and then: File:Update Table --------------------------- -Using apt-get to install binary packages: The most frequently used apt-get commands are 'update' and 'install' . To retrieve and scan the Packages.gz files, so that information about new and updated packages is available, run: sudo apt-get update To 'download and install' the especified deb package, run: sudo apt-get install packagename
Running apt-get with the -s option (No-act. Perform ordering simulation) will give you a list of all the packages that will be installed. apt-get -s install packagename For more info on using apt-get run: apt-get --help ---------------------------- Summary Check that the file /sw/etc/apt/sources.list has 10.3 in the deb lines. fink scanpackages (only needed the first time you do this) sudo apt-get update sudo apt-get install packagename Updating Fink emacs21-xaw3d in Panther I had installed emacs21-xaw3d before the update to Panther. Then, in Panther when I wanted to 'update build' emacs21-xaw3d I got the following error:
Then, I changed and built fink emacs21 package and it compiled without any issues. I had already xaw3d built and was "seen and built in", and as far as I can tell the end result is the same as emacs21-xaw3d and it works quite well till now. Panther default open source packages and Fink Here is a list of a number of packages that are provided by Fink and are already included with the default install of 10.3 (Some were in Jaguar as well):
Apple has added a number of new open source pacakges with each major release of OS X. But, keep in mind that sometimes the system versions lack important pieces. Like python on "Jaguar", which was missing the headers, so you couldn't build anything against it. From what I know, fink's philosophy till now, has been to keep providing a fink version of the package, even after Apple is providing their own. Maybe they don't trust Apple to be consistent in what they provide, like for example, when they used to provide wget, which fink relied on, and then at a certain point they switched to curl. Many users will already have the "fink" version of the library linked in to their packages, and upgrading becomes pretty tricky if they were to try to revert to Apple's version. Generally, I tend to follow Fink on this, as Apple is not always good about keeping packages "current", and fink does that more frequently. bus error after fileutils update There is a bug, apparently in 'gettext' when you run: 'fink rebuild fileutils ; fink install fileutils'. After that, running the simple command "ls" results in a bus error. To fix it, run first: dpkg -r --force-depends fileutils so that the rebuild doesn't get killed by crashing mv or cp commands. An then: fink rebuild gettext Or sudo dpkg --remove fileutils fink reinstall gettext fink reinstall fileutils compiling qt3-3.2.2-1 fails
Remove the qt3 packages before you rebuild qt3. You may need to use force: sudo dpkg -r --force-depends qt3 qt3-dev qt3-shlibs Then: fink install qt3 a root directory /sw exists "trying to install fink 0.6.1 after deleting all other fink files on os x 10.2.8. message "a root directory /sw exists. please see the read me file for update instructions, or for information on installing fink on a separate volume". You need to remove /sw if you are reinstalling Fink: sudo rm -rf /sw The "trailing slash" or "mv" bug
In Panther in some cases the mv command appears to not be able to handle trailing slashes. This is caused by the Stuffit Pro kext. Solution: Go to your Stuffit Pro Preferences in the "System Preferences" and desactivate "ArchiveViaRealName". /sw/bin/pathsetup.command; exit If you get the following message in your Terminal.app:
Your terminal preferences contain the instruction to run pathsetup. You probably pressed the "Use Settings as Default" in the Terminal when fink had opened the window automatically. To fix it, open the file com.apple.Terminal.plist in: ~/Library/Preferences and remove the entry for ExecutionString which probably reads like: <key>ExecutionString</key> <string>/sw/bin/pathsetup.command</string> to this: <key>ExecutionString </key> <string></string> /sw/fink/10.2 - /sw/fink/10.2-gcc3.3 If you're running 10.3, you can remove both directories to reclaim some space. If you are doing selfupdate-cvs, they will come back, however. Selfupdate-rsync leaves them alone.
/ Make Contact /drop me a line at: sao1@mac.com |
| MacOS X, Fink, X11, Unix ...and other related things |