On Thu, 2002-12-12 at 10:20, Justin Hallett wrote: > Sure but for new installs at least the user has a choice with it hard > coded then the user would need to mofy the fink code or every info file > he/she installs, I want to run deployment=10.2 and it would be much easier > for my to change it in a .sh file.
If you want to run it with it set to 10.2, then hack your fink, but it could potentially create broken binaries. I don't think it should be something that's set in a known user-modifiable directory, or you end up with users breaking things and not even knowing it. The packager should have to explicitly set it, I think. Most open-source programs are not aware of the intricacies of the OSX linker, so dying if the symbol doesn't exist is going to be expected behavior 99% of the time for the software we're porting to fink. Ignoring that is bad, in my opinion. ------------------------------------------------------- This sf.net email is sponsored by: With Great Power, Comes Great Responsibility Learn to use your power at OSDN's High Performance Computing Channel http://hpc.devchannel.org/ _______________________________________________ Fink-commits mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-commits
