From: Randall W. <rh...@ma...> - 2005-01-16 06:09:37
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Charly: Now I FINALLY UNDERSTAND what's going on. When I posted the build for GPG Keychain Access on Friday, I forked the code in CVS. A branch with tag v_0_7 will include the working code that is used to build version 0.7.0 and any bugs in 0.7.0 will be fixed under that tag leading to 0.7.1, 0.7.2, etc. The materials in the HEAD (no tag) will be used to build 0.8, 0.9,...,1.0, 1.1, etc. These are not building, as you can see because I still have files in a very rough state that have not been posted in CVS that the build is depending upon. Until I get 0.7.0 out of the door, I probably wont be able to touch GPG Keychain Access in the HEAD of the CVS repository. So to build 0.7.0, create a separate directory (I use Mac_GPG_Keys_0.7) beside your existing Mac_GPG_Keys directory and checkout module Mac_GPG_Keys with tag v_0_7 (or maybe tag V_0_7, I forget off the top of my head). Your build in that directory should work like a charm. On 16 Jan 2005, at 14:48, Charly Avital wrote: > Hi, > > with the most recent available release in CVS (1/16/2005 12:45 AM ET) > > <Keychain.tiff> - -- Randall Wood rh...@ma... "The ball is round. The game lasts ninety minutes. The rest is theory..." -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (Darwin) iD8DBQFB6gUXbc779cOt4kURAqhVAJ4iygla3wihucctU4d00DEXrTSEEQCgiJ9g 6BBUaqXvg676Jxbf2PnEHE0= =0MAT -----END PGP SIGNATURE----- |