Am Freitag, den 02.12.2005, 08:55 +1100 schrieb Daniel Kasak:

> You've got the right place. It's a matter of:

> - have you described the bug completely?

Maybe you can tell me how I should do this.

> 'modules could not be loaded' isn't completely describing things. How 
> did you try to load the modules? What happened when you tried this?

I simply deleted .e (for not to have a segfault) and logged in with
entrance to e17.  Then I get many popups could not load this or that
module - one popup for every module, so at least there is no module
loaded (in the menu 'Modules' shows (No loaded modules).

Is there a way to have a session with nothing exept an xterm in entrance
to choose?  Failsafe seems to load a wm (twm?), otherwise I could give
you backtrace from e17, but hum - how can I make gentoo not to strip all
the e17 binaries - this causes to have 'No debugging symbols' as far as
I know?

> - do the developers have the time to respond to your email?
> 
> As the devs have pointed out before, they're busy. I believe most have 
> full-time jobs, or study full-time, and code in their spare time. I'm 
> responding to you because I use Enlightenment, and I want to help the 
> project in whatever way I can. For me, that means responding to the 
> occasional question on the mailing list, as I can't code in C. 

I can code C, but I don't like to build all the apps by my own, so the
gentoo ebuilds are pretty good.  I could create a script which makes use
of patches, so I could send you patches for that.  But before I start
this (I would not code e17, I would only try to solve build errors or
segfaults - a segfaults normally is causes by a missing test (in C a if
clause), however, before I start, I would like to know if you could need
me, and I'd like to know how you work.  You can have patches from me
(diff -Nur).

> As for modules not loading ... my modules load. If you describe in more 
> detail what you're doing, maybe someone can point out what you're doing 
> wrong. In the case that you have actually stumbled across a bug, rest 
> assured that others will notice the bug, and when someone gets around to 
> it they will fix it.

I use the following script to update my e17.  You would need to know
about gentoos ebuild system to understand what 'emerge' does.

#!/bin/sh
for prog in eet dev-db/edb evas ecore embryo imlib2 imlib2_loaders \
        edje epeg media-libs/epsilon esmart emotion engrave ewl entice \
        entrance eclair e examine \
        engage e_utils e_modules elicit evidence \
        evfs
do
       false
       while [ "$?" -ne "0" ]
       do
       emerge --oneshot $prog;
       done
done

This gives you a hint for the order I use to rebuild all the things.
The while is that on cvs update failure the package will be tried again.

Maybe this helps, if not, just ask for more information.

Martin



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Reply via email to