Jess H. Brewer wrote: > Alexander Hansen wrote: >> Jess H. Brewer wrote: >>> Anyone else see this? >>> >>> # fink update-all >>> Information about 8618 packages read in 9 seconds. > . > . > . >>> The package 'gcc44' will be built and installed. >>> Reading dependency for gcc44-4.3.999-20090407... >>> Reading build dependency for gcc44-4.3.999-20090407... >>> Reading dependency for gcc44-shlibs-4.3.999-20090407... >>> Can't resolve dependency "xcode (>= 3.1.2)" for package >>> "gcc44-4.3.999-20090407" (no matching packages/versions found) >>> Exiting with failure. >>> >>> >> That would most likely be because you don't have Xcode 3.1.2 >> installed. gcc44 requires that version of Xcode to build. You'd have >> to download >> and install that. > > # fink apropos Xcode > Information about 8618 packages read in 3 seconds. > i xcode 3.1-1 [virtual package representing the > develop... > > OK, apparently you are correct; why didn't # fink update-all > find that? Let's do it by hand... > > # fink update xcode > Information about 8618 packages read in 7 seconds. > No packages to install. > xcode is _not_ a fink package, and is therefore not available via Fink. Our virtual package system only knows about what's on the system: it doesn't check for possible updates (I'm not even sure if that's possible).
$ fink info xcode Information about 8684 packages read in 2 seconds. xcode-3.1.2-1: [virtual package representing the developer tools] This package represents the C/C++/ObjC developer tools provided by Apple. If it does not show as installed, you can download it from Apple at: . http://connect.apple.com/ > So... why are packages getting updated with dependencies on a > version of Xcode that is not available as an update? > It's available; just not via Fink. > I understand that Xcode is not just any package, and that one > might worry about writing over Xcode 3.1-1 by force, lest some > other packages that are incompatible with Xcode 3.1.2 stop > working; That won't happen. Almost nothing has a _runtime_ dependency on Xcode. Those few packages which do happen to need some tools that it provides for installation purposes. > but if such hazards do exist, then why is gcc requiring > it for the new version to work? This seems to violate the whole > spirit of "satisfying dependencies". gcc44 needs stuff from the newest available Xcode to build. That is all. > > No doubt there was an announcement posted down at Vogon Central > and it is my own fault for not knowing I should have read it. > I apologize for my ignorance and humbly request an explanation. In general, it behooves users to migrate to later Xcode versions (and we do announce if there are situations in which a new Xcode is known to cause problems). Plus we're a small, volunteer, effort, and so we don't announce _everything_ that goes on. The situation is this: we use Apple's compilers from the Xcode Tools, but we don't repackage them ourselves (I don't even know if we can do so, legally). Since they aren't updated via Software Update, it's up to users to download an appropriate version if a package needs it. Fink is not a Linux distro, where _everything_ is included. We run on top of a commercial operating system, and are therefore subject to _its_ rules. -- Alexander Hansen Fink User Liaison ------------------------------------------------------------------------------ This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com _______________________________________________ Fink-beginners mailing list [email protected] http://news.gmane.org/gmane.os.apple.fink.beginners
