I have that in mind, I am currently focused on SUSE patchs, the most interesting, since the url that i have https://build.opensuse.org/project/packages?project=KDE:KDE3 are the only who v' ones who remain active to minor maintenance qt3 libraries and others kde3 related projects/soft

in fes hours i release a tarball in shutendouji.net

On Wed, May 11, 2011 at 1:42 PM, /dev/ammo42 <mickeytintincolle@yahoo.fr> wrote:
Le Wed, 11 May 2011 11:25:27 -0430,
PICCORO McKAY Lenz <mckaygerhard@gmail.com> a écrit :

> from slack patchs, the two patchs:
> qt-x11.diff.gz
> qt.x86.cflags.diff.gz
>
> Must no aplliet due the "qt-x11.diff.gz" its configured at configure
> time with -qt-gif parameter and the "qt.x86.cflags.diff" only apllied
> to x86 archs.
Anyway, Slackware-specific patches are usually not interesting because
since Slackware patches software as little as possible, the patches end
up being trivial. There are some exceptions: for example, polkit on
Slackware 13.1 was heavily patched to avoid having PAM in the
distribution (in 13.37 the patch seems to be merged in upstream), and
xfig comes with a lot of ancient, but still present, patches (some of
these are from February 2004).
>
> On Tue, May 10, 2011 at 3:18 PM, PICCORO McKAY Lenz
> <mckaygerhard@gmail.com>wrote:
>
> > ¬_¬u
> >
> >
> > On 5/10/11, /dev/ammo42 <mickeytintincolle@yahoo.fr> wrote:
> > > Le Tue, 10 May 2011 15:11:51 -0430,
> > > PICCORO McKAY Lenz <mckaygerhard@gmail.com> a écrit :
> > >
> > >> theres a refresh workaround  .. i consult htat reverification of
> > >> notifi Xrand , i applied that for comp backguard on minimal
> > >> builds:
> > >>
> > >> This patch replaces the old #0032 patch as actually just a
> > >> workaround. Taken from debian builds:
> > >>
> > >> --- a/src/kernel/qapplication_x11.cpp
> > >> +++ b/src/kernel/qapplication_x11.cpp
> > >> @@ -3407,7 +3407,8 @@ int QApplication::x11ProcessEvent( XEven
> > >>  #endif
> > >>
> > >>  #ifndef QT_NO_XRANDR
> > >> -    if (event->type == xrandr_eventbase + RRScreenChangeNotify)
> > >> {
> > >> +    if (event->type == xrandr_eventbase + RRScreenChangeNotify
> > >> +    || ( event->type == ConfigureNotify &&
> > >> event->xconfigure.window == QPaintDevice::x11AppRootWindow())) {
> > >>      // update Xlib internals with the latest screen
> > >> configuration XRRUpdateConfiguration(event)
> > > It's exactly the same patch.
> > >>
> > >>
> > >>
> > >> On 5/10/11, /dev/ammo42 <mickeytintincolle@yahoo.fr> wrote:
> > >> > Le Tue, 10 May 2011 14:31:00 -0430,
> > >> > PICCORO McKAY Lenz <mckaygerhard@gmail.com> a écrit :
> > >> >
> > >> >> please help:
> > >> >>
> > >> >> About the 67101 and 101516 (these dublicated of fisrt) The old
> > >> >> qt-copy patch #0032 seems was wrong, and the real problem is
> > >> >> in the X server as can i see
> > >> >> ttps://bugs.freedesktop.org/show_bug.cgi?id=2965 .
> > >> > Effectively, it seems to be a kludge.
> > >> > From man Xrandr:
> > >> >>The  XRRScreenChangeNotify  event  is  sent  to  clients  that
> > >> >>ask to be informed whenever the root window configuration
> > >> >>changes. Configuration changes may include resolution,
> > >> >>physical size, subpixel order (see XRender(3)), and rotation.
> > >> >>Note that changes to any or all of  these  could occur due to
> > >> >>external events (user control in the X server, a different
> > >> >>monitor/flat panel display being hot-plugged) and is not only
> > >> >>the result of a protocol/library request to the X server.
> > >> >
> > >> >>
> > >> >> I should remove this patch, any body removed from ARCH or slak
> > >> >> builds?
> > >> > I just removed it. Anyway, like every other qt-copy patch, it
> > >> > has never been included in Slackware, and it didn't prevent
> > >> > Slackware's KDE3 from working well. Keeping it would not
> > >> > introduce bugs, but just perhaps slow the library (but I don't
> > >> > think it would slow it much).
> > >> >> <snip>
> > >> >
> > >> > ---------------------------------------------------------------------
> > >> > To unsubscribe, e-mail:
> > >> > trinity-devel-unsubscribe@lists.pearsoncomputing.net For
> > >> > additional commands, e-mail:
> > >> > trinity-devel-help@lists.pearsoncomputing.net Read list
> > >> > messsages on the Web archive:
> > >> > http://trinity-devel.pearsoncomputing.net/ Please remember not
> > >> > to top-post:
> > >> > http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
> > >> >
> > >> >
> > >>
> > >>
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail:
> > trinity-devel-unsubscribe@lists.pearsoncomputing.net
> > > For additional commands, e-mail:
> > > trinity-devel-help@lists.pearsoncomputing.net
> > > Read list messsages on the Web archive:
> > > http://trinity-devel.pearsoncomputing.net/
> > > Please remember not to top-post:
> > > http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
> > >
> > >
> >
> >
> > --
> > Lenz McKAY Gerardo (PICCORO)
> > http://qgqlochekone.blogspot.com
> > Cofundador de Venenux;  debian based multimedia alike free only
> > zealots users (oh well, i try but..too many free guidelines buahhh)
> > http://shutendouji.net
> > creador de massenkoh linux; debian enhanchements for better up to
> > date support on stable brand, including non-free soft.
> >
>
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net
For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net
Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/
Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting




--
Lenz McKAY Gerardo (PICCORO)
http://qgqlochekone.blogspot.com
Cofundador de Venenux;  debian based multimedia alike free only zealots users (oh well, i try but..too many free guidelines buahhh)
http://shutendouji.net
creador de massenkoh linux; debian enhanchements for better up to date support on stable brand, including non-free soft.