Todai Fink Team tried building all unstable packages automatically.
You can check what package could not be built or installed here:
http://fink.sodan.ecc.u-tokyo.ac.jp/build/2005-03-26/
Notes:
* The most common error is insufficient BuildDepends. Especially
libiconv-dev is very frequently
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David R. Morrison wrote:
| Yes, probably we should say that patches for open source projects
| inherit the license.
I'm kind of late into the fray here (had a short vacation), but would
suggest that we notify submitters that we prefer .info and .patch
Peter O'Gorman wrote:
I'm kind of late into the fray here (had a short vacation), but would
suggest that we notify submitters that we prefer .info and .patch files to
be placed in the public domain, but that explicit licenses can be added to
comments in the .info file, or the patch file, if
Peter O'Gorman wrote:
[]
I don't think that a new field is necessary, and do believe that the time
available to implement any solution is very short, so I suggest that we
start implementing this as soon as practical.
I would like to have one point cleared up in my understanding. Let me
first say
Martin and Jean-Francois:
-fabi_version=2 is not available under gcc 3.3.
What you get when you compile using gcc 4.0 and -fabi_version=1 is all of the
new features of gcc 4.0 *except* the change in ABI.
Libraries compiled with abi_version=1 are not compatible with libraries
compiled with
