This is unstable.
Keith On Jan 13, 2004, at 7:57 PM, Ben Hines wrote:
On Jan 13, 2004, at 4:32 PM, Ben Hines wrote:
On Jan 12, 2004, at 11:40 PM, Martin Costabel wrote:
Ben Hines wrote: []ld: Undefined symbols: _rsvg_set_default_dpi
This one has been answered many times (see also the post "fink-gnome-core black hole" to fink-devel). You need to remove the old version before compiling the new one. There is no good strategy in such a situation as has been seen for many other packages in the past.
No, i should not have to do that. There are hacks to get around such situations, i have fixed them before in many packages.
And seriously folks, i am still sick of this "user must {force depends, remove old first, manually do <foo>} to use the new version of my package" bullshit which has been happening more and more recently. There are solutions for everything. The last, last, last resort is having the user do something. If a temp upgrade-package is required, then that is preferred over having the user do something. If modifying %p is required, then that is preferred to having the user do something. Often there are much easier build time fixes. (as in this case) There is always a way. If a user must manually do something to update a package, please file a bug on the bug tracker.
These situations are NOT acceptible to fink users. These situations STILL cause people to leave fink.
And no martin it doesn't matter that is has been 'answered many times' by the gnome maintainers - it has never been asnwered (actually, until sunday - once) on fink-devel or fink-users which are the fink mailing lists. fink-gnome-core is the maintainer for the gnome packages, not a fink discussion forum. I refuse to subscribe to it. Is it in the FAQ? This is a package bug, not a user problem. Since it is a known 100% problem that you know about, why do you not detect it when building and error out with a useful message? This is just bad package maintenance.
Lets see, here... its using the not-yet-installed lib? Just move the order of the link line, looks like this works, it builds just fine with it:
SetLDFLAGS: -L./.libs
Works fine. No 'remove this first' crap needed. If there are problems with that fix, i am sure we can find another one.. even if it means manually linking the file in the installscript. TRY, people. This is IMPORTANT. That is a REALLY EASY FIX. Yes it is 'hackish'. that is preferred to telling fink users to do things. If you really hate it, remove the line in a year when most folks will have updated. We've had far worse hacks in fink packages for a long, long time.
-Ben
------------------------------------------------------- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html _______________________________________________ fink-gnome-core mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-gnome-core
------------------------------------------------------- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
