trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: May 2011

Re: [trinity-devel] Qt3 code analysis, qt-x11-3.3.8b source compared to trinitydesktop (svn)

From: PICCORO McKAY Lenz <mckaygerhard@...>
Date: Wed, 18 May 2011 10:00:30 -0430
Please i attached a README file with a few analysis of many patches i
found in others distributions and also network:

Perdon my english on first readme, the file well documented its the
changelog 3.3.8c but this not reflect patch work, the readme file
attached its a stub and pre file for documentation, the complete work
will be in the msktoo blog of netter's funtoo implementation (funtoo
its a geento author/creator linux but better implemented)

I now testing compiled versions and runtime performance, I think the
decision to  load a patched version of qt3 without analyzing the
applied/apply patches added and extra work load for the development of
the trinity desktop team, causing loss of time if I was already
examining the issue.

I've note that most Linux distributions do patches just to get out of
step, the developers of these distributions not provide something
really analyzed the library, while in debian patches are highly tested
and placed with care. (only two debian patches makes library take
debian specific, the rest is highly useful and distro independent!!!).

I propose that after finishing my tests compare my tarball (which will
be now tested) which exists in the repository. This is because as I
have analyzed, implemented and documented patches on the previous
version, work that are minimal and necessary for prevent build faille
or runtime errors in future!

On Tue, May 17, 2011 at 11:33 PM, /dev/ammo42
<mickeytintincolle@...> wrote:
>
> Le Tue, 17 May 2011 21:23:42 -0500,
> "David C. Rankin" <drankinatty@...> a écrit :
>
> > On 05/16/2011 10:38 PM, Timothy Pearson wrote:
> > > If something seems unusual (e.g. that nastiness you posted above),
> > > please look through the tarball I posted to this thread earlier to
> > > see if there are any patches that may have caused the problem.  If
> > > so, just let me know and I will reverse the patch in question.
> > >
> > > Tim
> > >
> >
> > Will do,  I haven't had a chance to revisit Qt3 in the past few days.
> > Mickey? (/dev/ammo42) has done a good deal of looking at it. We will
> > have to compare notes and get a good bullet-proof baseline Qt3 setup
> > and see what patches can be added to the svn tree that will work with
> > *all* distributions + gcc46 to minimize the distro specific/x86_64
> > specific patches and build scripts.
> I did not review the largest patches (one of the Debian ones has a size
> of 1 MB; for such a size I just count on its Debian/Ubuntu test of
> time :)).
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: trinity-devel-unsubscribe@...
> For additional commands, e-mail: trinity-devel-help@...
> 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.

Attachments: