Linked by Kostis Kapelonis on Tue 15th Feb 2011 22:57 UTC
Thread beginning with comment 462682
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/22/13 22:23 UTC
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
More News »
Sponsored Links



Member since:
2009-08-11
Ill preface I appreciate the arch devs for packaging pre release software. Generally my experience with packaged e17 & efl has been shaky at best. For arch using repo package my cpu usage was relativley high to me 20-30, with composite more like 40-60%. Compiled I rarely go above 10%, including compositing. I don't know what it is, but self compiling just worked better. I used easy_e17 for a while and switched to my own package builds later. Archs package were pretty bare of configuration flags, however i think a lot of options are auto enabled. So I don't know where the problem is.
None the less I'm happy to hear this I've been an e17 user since 2005, prior to that an e16 user. I have had great experiences with e17.