On Fri, Jul 15, 2011 at 08:09:57PM -0400, Benjamin Johnson wrote: On Fri, 15 Jul 2011 19:52:03 -0400, Roger <rogerx.oss@gmail.com> wrote:
On Fri, Jul 15, 2011 at 11:29:15AM -0400, Benjamin Johnson wrote:
FWIW, those dialogs have always been broken on Windows. I basically had to write my own Fl_Native_File_Chooser class (although Windows' dialogs are much nicer than FLTK's, anyway).
I'd say just include a "known good" FLTK2 release in the Dillo tarball, and modify the build system to use that copy instead of the system one. As an added bonus, it might make Dillo more attractive to Linux distributions, since they don't have to add an unreleased dependency library to include an up-to-date Dillo package.
Just a thought, ~Benjamin
This then defeats the purpose of a source based distro such as Gentoo.
It's a common enough trick -- OpenOffice.org does it, Audacity does it, basically any big-name open source project you can think of includes at least one dependency library in the stable tarballs because the upstream developers can't keep a stable API or functional code longer than ten minutes.
I can't argue this one. FLTK has made their bed on this. :-/
If the distributions wish to change things, that's their prerogative; I mean, Debian's constitutionally incapable of leaving upstream code unmolested, and I'm sure anyone else who maintains an ebuild/RPM/BSD port can figure out how to patch it back to do things their own way. At least you've made an attempt. It may work, it may not, but it's still better than doing nothing but whine about how no distributions will ship your code because of a trivially avoidable technicality.
I was thinking of providing a --use-static-fltk configure option or something. This way, when things do get stable, a distro can chose to build with external libs.
~Benjamin