Torrey Lyons [[EMAIL PROTECTED]] wrote: > I think there's one good answer and one okay answer, but having KDE > depend on xfree86-extras is the worst of all worlds. > > Good answer: I suggested to the Fink folk and I'm going to push this > point harder that they install shared libraries outside of > /usr/X11R6/lib. There is only one package that appears to need a > shared libXv and that package can be modified to add an extra -L to > something like /sw/X11R6/lib. This way KDE and all the other Fink > packages will be identical everywhere. As you noticed there is no way > to get them to be identical everywhere otherwise, which loses the > whole point of xfree86-extras. If every package has to depend on it > anyway, it might as well be part of xfree86-base.
Yeah... I was referring to that... even if the dylibs are installed in, say, /sw/lib, KDE built on fink will still find them, because it's looking for tons of other stuff there. Personally, I would rather we dump the dylibs for Xinerama and Xv altogether, and just say "if you've been running recent Fink unstable, you may have to rebuild some packages that build against X". The XFree86 team doesn't want them dynamic, and they don't match other Darwin XFree86 builds, so it's just a bad thing to propagate. The only reason it's there is to fix build issues with a single package in fink unstable. We've made it very clear that the KDE binaries are not guaranteed bug-free stable binaries, and that the things built in the KDE tree are from fink unstable. ...and fink unstable is exactly that. It's the place we try things out, and implement new policies. It should be expected that things can be wrong, and need to be backed out. The only real reason for keeping the dylibs is to retain backwards compatibility with binaries that were never really officially supported, only provided as a convenience to avoid a 2-day build for every single end-user. > In any case, if you want KDE to be distributable outside of a Fink > environment you have to make sure you don't use shared libXv. (I > would hope eventually KDE will end up being a poster child for > Apple's forthcoming package manager.) If doing this using my "okay > answer" happens to make things a little confusing for Fink users, > that is the fault of a poor design decision by the Fink maintainers > and not yours. Yes, I would really like to see it be easy to build KDE anywhere on Darwin, be it pure Darwin, a MacOSX application bundle, fink, or whatever... The best way to be sure of that is to make sure weird inconsistencies like this don't happen. I guess if the KDE folks don't mind, I'll look into implementing checks in the KDE build to force linking against the static libraries only. I'm guessing they wouldn't have a problem with it if it's XFree86's recommendation, but even if they don't, it shouldn't be difficult to maintain in our CVS if need be. -- Benjamin Reed a.k.a. Ranger Rick ([EMAIL PROTECTED]) http://ranger.befunk.com/ "Oh, and as long as I've got you here, tell that French DJ Tricky to move out ... and tell him to stop letting in strangers to listen to his new 'beats'." -- Space Ghost, to his wife, Bjork Gudmundsdottir _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
