On Wed, 2012-12-19 at 11:56 -0500, Gregory Maxwell wrote: > On Wed, Dec 19, 2012 at 11:53 AM, Dan Williams <dcbw@xxxxxxxxxx> wrote: > > It's the other way around. If libfoo 1.0.0 linked with -lbar and -lm, > > and then you upgraded to libfoo 1.0.1 which *no longer* links to -lm, > > now stuff that links to libfoo might fail if those things did not > > specifically request -lm themselves when they were built, and they need > > it. > > Ah. I read your statement backwards. > > I think we're in agreement. Everyone should (really, must) link their > own dependencies explicitly, and pkgconf style config lines should > generally only list the library itself to avoid creating a situation > where the caller fails to correctly identify its dependencies and > doesn't know it. But maybe fltk intentionally does something > inadvisable here. Yes, it appears to, but as a presumably fltk upstream sanctioned mechanism that allows fltk apps to run one command to get the commonly linked libraries, instead of having to link to all of them manually. Yes, that's not best practice. But at the same time, it does (a) make fltk developers' lives easier, and (b) isn't something Fedora is likely to change upstream. Possibly we just have to live with it, otherwise we periodically get to listen to a few surly, abrupt, and un-courteous fltk users. Dan -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
