"KDE Improvement Project" (KIP) - KDE 3.5.4 ebuilds

[sklettke]

The previous ebuild, 0.4.5, for KDE 3.3.1 compiled correctly. The new ebuilds for 0.5.0, however, fail on kdebase with this:

Code: Select all

konq_infolistviewitem.cc: In member function `virtual void
   KonqInfoListViewItem::paintFocus(QPainter*, const QColorGroup&, const
   QRect&)':
konq_infolistviewitem.cc:259: error: `sectionRect' undeclared (first use this
   function)
konq_infolistviewitem.cc:259: error: (Each undeclared identifier is reported
   only once for each function it appears in.)
make[3]: *** [konq_infolistviewitem.lo] Error 1
make[3]: *** Waiting for unfinished jobs....
make[3]: Leaving directory `/var/tmp/portage/kdebase-3.3.1/work/kdebase-3.3.1/konqueror/listview'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/var/tmp/portage/kdebase-3.3.1/work/kdebase-3.3.1/konqueror'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/kdebase-3.3.1/work/kdebase-3.3.1'
make: *** [all] Error 2

!!! ERROR: kde-base/kdebase-3.3.1 failed.
!!! Function kde_src_compile, Line 142, Exitcode 2
!!! died running emake, kde_src_compile:make
!!! If you need support, post the topmost build error, NOT this status message.

[taskara]

thanks for the heads up, I'm talking to Andrunko about it, and will let u know when there is a fix..

in the mean time I'll put v0.4.4 back in download section

ta

[StifflerStealth]

Changelog:
v0.5.1: (2004-Oct-26)
* fixed compile error in kdebase/konqueror/listview.

Looks like it's fixed already. Happy compiling.

[taskara]

Changelog:
v0.5.1: (2004-Oct-26)
* fixed compile error in kdebase/konqueror/listview.

Looks like it's fixed already. Happy compiling.

Yep, andrunko emailed me - new version 0.5.1 ebuilds are out.

The only file that has changed is kdebase.diff so if you were already compiling v0.5.0, then pick up where you left off with kdebase.

-c

[taskara]

Version 0.5.2 is released, and ebuilds patched accordingly.

only kdebase needs to be re-built if upgrading from v0.5.1, and corrects a draw problem in detailed mode under konqueror.

[StifflerStealth]

Version 0.5.2 is released, and ebuilds patched accordingly.

That's my luck. I just finished compiling version 0.5.1. *goes off to comple kdebase again*

[taskara]

Version 0.5.2 is released, and ebuilds patched accordingly.

That's my luck. I just finished compiling version 0.5.1. *goes off to comple kdebase again*

lol

well 0.5.1 had a bug in detailed view mode, if you don't use detailed view you don't need to update

also, u only need to re-build kdebase

[StringCheesian]

Has anyone been able to build this with unsermake? unsermake seems to be choking on kde with these patches for me. Regular make is working fine so far.

[sklettke]

Hello,

I am sorry to report that the rubberband works horribly.
Here are screenshots of the problem:

http://rencade.raphit.net/~sundance/RubberBandBug1.png
http://rencade.raphit.net/~sundance/RubberBandBug2.png

It looks like the rubberband is not erased between two successive positions of the mouse.
This seems to be the same problem jmercer was having.

Any idea what could be up?

Thanks!

I was having this exact same problem until I upgraded to the latest X.org.

So, make sure you are using the latest kde improvement patchset from the top of page 1 and then upgrade to X.org. This involves unmerging Xfree86... But, everything worked flawlessly when switching over. After X.org was emerged I just ran an etc-update and startx to get back in kde. And now the rubberband works great!

Scott

[taskara]

Hello,

I am sorry to report that the rubberband works horribly.
Here are screenshots of the problem:

http://rencade.raphit.net/~sundance/RubberBandBug1.png
http://rencade.raphit.net/~sundance/RubberBandBug2.png

It looks like the rubberband is not erased between two successive positions of the mouse.
This seems to be the same problem jmercer was having.

Any idea what could be up?

Thanks!

I was having this exact same problem until I upgraded to the latest X.org.

So, make sure you are using the latest kde improvement patchset from the top of page 1 and then upgrade to X.org. This involves unmerging Xfree86... But, everything worked flawlessly when switching over. After X.org was emerged I just ran an etc-update and startx to get back in kde. And now the rubberband works great!

Scott

Thanks for the heads up Scott, I'll suggest that people use Xorg on the front page.

And StringCheesian, I'm not sure.. I'll add that it doesn't work with unsermake at the from page..

[Realmaker]

Is it possible to run composite with this ebuilds? If no, is there any possibility to have composite in kde?

[jimmybfan]

does this entry from the changelog mean that qt no longer needs to be patched?

Code: Select all

* modified qt patches to kde ones so is more easy to get them accepted by kde developers.

[taskara]

does this entry from the changelog mean that qt no longer needs to be patched?

Code: Select all

* modified qt patches to kde ones so is more easy to get them accepted by kde developers.

I believe Andrunko is moving away from having to patch qt, so that the patches are more attractive to kde devs, but not done yet..

[taskara]

further to qt, here is Andrunko's reply

[qt needs to be patched] just for the iconview rubberband effect and the rounded selection. the
rounded selection i believe can be moved, but the rubberband can't
cause the current qt implementation doesn't allow me to access a
private member that i need to draw the rubberband.

cheers
Andrunko

[GentooBox]

further to qt, here is Andrunko's reply

[qt needs to be patched] just for the iconview rubberband effect and the rounded selection. the
rounded selection i believe can be moved, but the rubberband can't
cause the current qt implementation doesn't allow me to access a
private member that i need to draw the rubberband.

cheers
Andrunko

cant you rename the ebuilds to something else that the kde versions in portage.

It makes some funny bugs on my system if i just put the ebuils in my overlay and emerge them.
Does it work on you computer ?

also, i removed the digest and manifest files from your package and redigested it myself, and it reported an error - something to do with the qt ebuild missing some patch.

[taskara]

cant you rename the ebuilds to something else that the kde versions in portage.

It makes some funny bugs on my system if i just put the ebuils in my overlay and emerge them.
Does it work on you computer ?

also, i removed the digest and manifest files from your package and redigested it myself, and it reported an error - something to do with the qt ebuild missing some patch.

hmm you're right, thanks. qt can't find that file.

can you try doing a digest QT in your usual portage tree?

Code: Select all

ebuild /usr/portage/x11-libs/qt/qt-3.3.3.ebuild digest

Also, could you search your entire hdd for that patch it wants? I copied the ebuild from qt-3.3.3, so if it needs it, then it should be on your hdd somewhere, like the x11-libs/qt/files direcory.

let me know what you find!

also, heres the md5sum for kde-3.3.1.perrty.v0.5.2.tar.gz:
689462c01c3d8f4ed237ee60a746be43

incase it's corrupt.

Also, you can re-name the ebuilds to whatever you like - they are kde 3.3.1 ebuilds because you can't have perrty kde and normal kde on your system at the same time, and if you call them something else, your computer won't know you have kde installed, and you'll have to inject the kde packages, and it just gets messy

but you shouldn't have any trouble putting them under your portage overlay dir..

[GentooBox]

# emerge qt --digest
Calculating world dependencies ...done!
>>> Generating digest file...
<<< qt-x11-free-3.3.3.tar.bz2
<<< qt-x11-immodule-unified-qt3.3.3-20040910.diff.gz
Traceback (most recent call last):
File "/usr/bin/emerge", line 2990, in ?
retval=portage.doebuild(y,"digest",portage.root,tmpsettings,edebug,("--pretend" in myopts))
File "/usr/lib/portage/pym/portage.py", line 2520, in doebuild
return (not digestgen(aalist,mysettings,overwrite=1))
File "/usr/lib/portage/pym/portage.py", line 1950, in digestgen
mydigests=digestCreate(myarchives, basedir, oldDigest=myolddigest)
File "/usr/lib/portage/pym/portage.py", line 1886, in digestCreate
raise portage_exception.DigestException, "Size mismatch during checksums"
portage_exception.DigestException: 'Size mismatch during checksums'

qt-x11-immodule is nowhere on my box.
btw: there is a qt-3.3.3-r1 ebuild in the portage tree, maby you should use that ebuild instead of qt-3.3.3

[GentooBox]

I removed the Manifest and digest file and tryed again.

qt # ebuild qt-3.3.3-r1.ebuild digest
>>> Generating digest file...
<<< qt-x11-free-3.3.3.tar.bz2
<<< qt-x11-immodule-unified-qt3.3.3-20040819.diff.gz
!!! We have a source URI, but no file...
!!! File: /usr/portage/distfiles/qt-x11-immodule-unified-qt3.3.3-20040819.diff.gz

the qt-x11-immodule file is only downloaded when the immqt USE flag is enabled, but why does it complain about the file when its disabled (the USE flag).

[GentooBox]

I just compiled the 5.2 version, and it's really nice

No flicker and a smooth movement.
Thanks.

[taskara]

version 0.5.5 released

see initial post for details

-c

[wiSHmaKeR]

Yesterday I made myself try GNOME more serously, and now I see what were you trying to do with these patches

[ryujin]

Hello,

I am sorry to report that the rubberband works horribly.
Here are screenshots of the problem:

http://rencade.raphit.net/~sundance/RubberBandBug1.png
http://rencade.raphit.net/~sundance/RubberBandBug2.png

It looks like the rubberband is not erased between two successive positions of the mouse.
This seems to be the same problem jmercer was having.

Any idea what could be up?

Thanks!

I was having this exact same problem until I upgraded to the latest X.org.

So, make sure you are using the latest kde improvement patchset from the top of page 1 and then upgrade to X.org. This involves unmerging Xfree86... But, everything worked flawlessly when switching over. After X.org was emerged I just ran an etc-update and startx to get back in kde. And now the rubberband works great!

Scott

Thanks for the heads up Scott, I'll suggest that people use Xorg on the front page.

And StringCheesian, I'm not sure.. I'll add that it doesn't work with unsermake at the from page..

Trying to get this beautifull eyecandy on kde but unfortunately Im having the same problem as above (see snapshots). When I select several files in the Desktop or in icon view on konqueror I just get a dark blue box as seen in second screenshot. I dont see the problem when in list view on konqueror.

I have a new installation of gentoo with:

xorg 6.8.0-r1
nvidia 1.0.6111-r2
and v5.5 of the ecandy patches.

any ideas?? how to fix this??

I also have the RenderAccel set, and compiled qt, kdebase, kdelibs and kdeartwork with the patches.

ryujin

[taskara]

Ryujin,

could you try it witOUT nvidia driver? just the xorg nv driver?

I've compiled 5.5 on 4 machines over the last week and they all have worked

cheers

[ryujin]

Ryujin,

could you try it witOUT nvidia driver? just the xorg nv driver?

I've compiled 5.5 on 4 machines over the last week and they all have worked

cheers

Found the problem... When I recompiled I did it with the ~x86 accept keyword and got qt-3.3.3-r1 patched and installed instead of qt-3.3.3. So NVidia drivers have nothing to do.

I downgraded to qt-3.3.3 and now everything is beautifull... thanks for the patches.

Ryujin

[taskara]

Ahh, ok thanks.. I'll check the latest stable gentoo kde / qt ebuilds and release an updated version of the patched ebuilds.

-c