-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Monday, March 18, 2002, at 09:27 PM, Rich Ramos wrote: > >>> >> What am I doing wrong now? >>> > >>> > Nothing. Binaries aren't available for the bleeding-edge cvs >>> packages. >>> >>> But I didn't think that 0.3.2a was bleeding edge, it was released on >>> 1/16. >>> >>> Unless there is a difference between 0.3.2a and 0.3.2a-cvs, if that >>> is the >>> case can I go back to 0.3.2a (no cvs)? >> >> Well, I guess the important thing here isn't really that 0.3.2a >> version, >> but that your local copy of the CVS catalog is up to date. CVS is >> updated >> continually, and the version information for the catalog isn't. By >> running >> the CVS update command, you have brought your local catalog into sync >> with >> the public one, and can begin upgrading your local software to, yes, >> the >> bleeding edge versions of anything you have installed. > > Ok, maybe I'm not asking the right question or maybe I don't really > understand what I'm talking about (probably the latter. Or maybe the > problem is that I'm currently sitting in an IETF meeting on IP storage > and I'm trying to pay attention to the presentations as well as fix my > problem at the same time :) > > What if I don't want to be bleeding edge? What if I just want to bring > everything up to date with the last point relase 0.3.2a? > > The only reason I did the cvs update was because that was a suggestion > to fix my last problem which started this thread and that was just > trying to go from 0.3.1 to the point relase of 0.3.2a. Ok, from what I understand, when you update with CVS, you get all the package info for all the current packages, stable and unstable. if you are only using stable (the default), then you get the advantage of getting the updated packages between binary releases. stable is stable, for the most part. unstable is stableish/not usually bleeding edge, but it can be sometimes. I think though, that pre built binaries are only available for each binary release, ie. if you want to use the newest stable versions, use fink install <packagename>, or fink update-all to update everything you have installed to the newest stable version. I hope this helps. - -chris zubrzycki - - -- PGP public key: http://homepage.mac.com/beren/publickey.txt ID: 0xA2ABC070 Fingerprint: 26B0 BA6B A409 FA83 42B3 1688 FBF9 8232 A2AB C070 _________________________________________________ This message is encoded using the Rot-26 encoding method. Unauthorized decoding of this message may result in extreme penalties under the DMCA. These penalties include, but are not limited to: US$100,000 fine, life imprisonment, castration, death, limp hair, terminal halitosis, and amputation of the extremities. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (Darwin) Comment: For info see http://www.gnupg.org iD8DBQE8lqZR+/mCMqKrwHARAuYrAJ9zQK6WJ165aykFy6ZQ35AA6TZo5ACg3r9v p7g0klMdjAjbxelxon06uIY= =7eLN -----END PGP SIGNATURE----- _______________________________________________ Fink-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-users
