On Mon, 18 Mar 2002, Rich Ramos wrote: > However I'm having a follow on problem. Based on the input earlier I > went with the 'fink selfupdate-cvs'. (which seems like it agrees with > the link). Now, I have what seems the be the latest install and package > version: > Package manager version: 0.9.8 > Distribution version: 0.3.2a.cvs
Good, you're up to date there then. > And there are packages now marked with '(i)', which I want to get > updated. But if I run dselect or apt-get upgrade it doesn't think > that there is anything to upgrade. The last messages "fink selfupdate-cvs" gave you should have given you your answer here: you need to run "fink update-all" in order to build [from source] whatever needs to be updated. > If I run fink upgrade-all it downloads the source and starts building > from scratch, which I don't want to do if the binaries are available to > install. I think it's safe to assume that apt-get and dselect are going to lag behind the source code availablity for most Fink packages. Generally, binaries of open source software like this becomes available later, even much later, than the raw source versions. Building from source can take a while, but it's usually not *that* bad. When running update-all, if you're way out of date and have to upgrade a couple dozen packages, you can just leave that Terminal running in the background while you're doing other work (or leave it going over lunch, or overnight, or what have you). Once the source tarballs are downloaded, Fink basically goes on autopilot and can be left alone. -- Chris Devers [EMAIL PROTECTED] Apache / mod_perl / http://homepage.mac.com/chdevers/resume/ _______________________________________________ Fink-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-users
