Stabilize x11-libs/fltk-1.1.7-r2.
Changes from 1.1.7 to 1.1.7-r2: 07 Jul 2007; Mike Frysinger <vapier@gentoo.org> fltk-1.1.7-r2.ebuild: The amd64 patch is *not* amd64 specific, so apply it for everyone. 16 Jun 2007; Diego Pettenò <flameeyes@gentoo.org> +fltk-1.1.7-r2.ebuild: Fix fltk-config not to report the C(XX)FLAGS used to build fltk. 16 May 2007; Samuli Suominen <drac@gentoo.org> +files/FLTKConfig.cmake, +fltk-1.1.7-r1.ebuild: Install FLTKConfig.cmake and FLTKUse.cmake for bug 175006. No major changes in the code and two months in the tree. So, stabilisation seems reasonable to me.
Um, if we look at FL/Fl_Spinner.H, we see: double maxinum() const { return (maximum_); } double mininum() const { return (minimum_); } at lines 130, 132. These are wrong (should be maximum, minimum, of course). Is this something to worry about? (Some applications --- e.g., ruby-fltk --- will not build without a fix. Yes, I know ruby-fltk is not in our tree, but that does not stop me from playing with it.) I don't think this is a regression; I am asking if it's worth awaiting a patch. Otherwise, fltk-1.1.7-r2 seems fine on sparc; I'm just awaiting your recommendation.
Applied the following fix from latest 1.1.x snapshot: double maxinum() const { return (maximum_); } + double maximum() const { return (maximum_); } void maximum(double m) { maximum_ = m; } double mininum() const { return (minimum_); } + double minimum() const { return (minimum_); }
Sparc is stable.
x86 stable
Stable for HPPA.
alpha/ia64 stable
* QA Notice: Pre-stripped files found: * /var/tmp/portage/x11-libs/fltk-1.1.7-r2/image/usr/bin/fluid Marked stable on amd64.
stable on ppc
ppc64 stable
@mips: it's no worth to stable -r2. -r3 stabilization will come soon.
