Ok. It's all clear now. It's certainly possible that this should have been obvious to me and I missed it. But if others are falling into the same confusion as myself, may I be so bold as to suggest the following news item?
"Note: When deciding whether to install in the default mode or the 64-bit-only mode, keep the following in mind: A small number of packages are available as 64-bit in the default mode, it is not strictly 32-bit. Conversely more and more packages are becoming available in 64-bit-only mode. You can identify 64-bit packages available in the default mode by searching the the package database for and looking for results with "-64bit" in their names. You can identify packages available in 64-bit-only mode by using the advanced search and specifying "Architecture: Intel (64-bit)" (these will not have -64bit in their names, and this will not return any 32-bit packages). Remember to include your preferences of distribution tree (stable, unstable, etc) when making this decision." Thank you so much for your quick responses and help! ;-) Avram On 11 Jan 10 , at 3:55 PM, Alexander Hansen wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 1/11/10 3:07 PM, Avram Dorfman wrote: >> I was not criticizing anybody's efforts. I was merely trying to point out >> that the only two pieces of info available on choosing between 32 bit and 64 >> bit conflict with each other - the home page news item and the bootstrap >> script. >> >> One says you either choose 32 bit or 64 bit. The other says you choose >> between 64-only and a 32-bit mode with some 64 bit packages. >> > The language in the news item wasn't completely precise. That in the > bootstrap script is more so. > >> Is it possible to tell from the package search which packages are available >> as 64-bit in the default mode? How about which are available in the 64-bit >> mode? >> > > They have "64bit" in their name. E.g. look at > > http://pdb.finkproject.org/pdb/browse.php?name=64bit&summary=64bit > > All packages are built as 64-bit in the 64 bit mode, so the "*64bit*" > packages don't exist there. > >> I assume that Architecture: 64-bit weeds out the 32-bit packages > > In the sense of "Packages that build on 32-bit but not 64-bit". > > , but I can't tell how to weed out the modes. Does "Distribution: > Supported (10.5 and 10.6)" refer to the default mode? Or is that merely > an logical "and" of "Distribution: 10.5" and "Distribution: 10.6"? In > which case, how can you tell which modes a given 64-bit package will be > available in? > > That's a typo, actually. "Supported" means 10.4 || 10.5 || 10.6 , but > yes, it's the default. > >> >> Thanks, >> Avram >> > > <snip> > - -- > Alexander Hansen > Fink User Liaison > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.10 (Darwin) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ > > iEYEARECAAYFAktLkF4ACgkQB8UpO3rKjQ8WewCgj1n0ifUf65Ljt1h1HpIQzzba > rmEAnR76fpbebF0WZ4KMGH/eDDlVaFIF > =udYm > -----END PGP SIGNATURE----- ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Fink-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fink-users
