-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 5/3/10 1:12 PM, Jack Howarth wrote: > I think there is a fatal flaw with the concept of > having every gcc4x package contain a gcc split-off > such that the newest available FSF gcc is always used. > The packages that BuildDepends on gcc must also Depends > on a particular gcc4x-shlibs. How exactly will fink > dynamically update the Depends field in the info file > to depend on the particular gcc4x release which happens > to be building via the BuildDepends on gcc. I simply > don't see how this could be done without a major > enhancement of fink to provide a mechanism to reset > the Depends field from with in the scripts of the > info file. > Jack >
A precedent is "python": $ fink dumpinfo -fallversions python Information about 10108 packages read in 1 seconds. allversions: b 1:2.4.4-1 b 1:2.5.4-1 b 1:2.6.4-1 bi 1:2.6.4-3 And in that case we _don't_ have packages *depend on 'python' unless they need just _a_ python and don't do anything to code a version." So for packages where none of the libraries from FSF gcc get linked, perhaps a BuildDepends on 'gcc' would be OK. I'm in agreement with Jack: without automatic shared-library dependency updates (and revision updates?) there just does not seem to be a feasible shortcut option here except as noted above (and I don't have any examples). - -- Alexander Hansen Fink User Liaison -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkvfCHMACgkQB8UpO3rKjQ+TvwCePClsIg/BSX0tCydFeowjRw3J t4gAn3X995tWbS2Lf+DmxTL/nM7ycOzn =pE10 -----END PGP SIGNATURE----- ------------------------------------------------------------------------------ _______________________________________________ Fink-devel mailing list [email protected] http://news.gmane.org/gmane.os.apple.fink.devel Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-devel
