but first line says:
#!/bin/sh
sudo emerge ....
#!/bin/sh
sudo emerge ....

Try out this script which I use to detect whether there is an update to an already installed package (by noting the output of the cvs command). If there has been an update, then that package is emerged, and all other packages which are listed after that package are also emerged(since they depend on that package). However, you should add the additional packages you want to emerge to that list in the correct order. (The list of packages, E_LIST, in that script are the ones which I use and there are many more packages of enlightenment available).c0uchm0nster wrote: Anyways - I guess I just have to wait until epsilon is working in cvs again - but I'm curious as to a few things I was hoping people could clear up for me:
Since this is cvs I assume there's no automatic way for emerge to tell me if the packages are the same version as what I've got installed or if there's an update, correct?
I think one should update all packages which depend on a package which you have just updated. Thus, if you update epsilon then you should update all packages which are listed after epsilon in this list .How often to updated packages (like epsilon) break with dependencies to other updates? This one's kind of confusing so let me explain:
I've already successfully emerged/built about 8 of the ~38 packages before epsilon failed. What are the chances that once the epsilon package is fixed I'll have to also re-emerge those 8 packages I've already got (to put it in it's simplist: Are the packages an all or none situation in regards to updating?)
You can check the cvs commits at http://cia.navi.cx/stats/project/e/ They are updated daily, so I think the enlightenment project is very active.and lastly: how active is the e17 project? mainly: how often do you guys (& girls?) update? and how fast are broken packages fixed in the cvs and/or portage?
Thanks

It's an enlightened filesystem daemon - it's not in use by any application yet, but in the future it'll be used for various things. Currently there is no point installing it, from a users point of view at least.ppurka wrote:I have noticed a lot of commits to efsd lately. But it is not even mentioned in the get-e.org package list. Is it some new component of e17? There doesn't seem to be any package in portage either, by the name of efsd.
TIA
Careful of CFLAG useage. Some of them are added by your -O* options and manually adding them is just redundant. Some of them are known to break things...badly. You might check this page for gcc optimizations, or simply:Cinder6 wrote: EDIT2: Well, conservative CFLAGS didn't do the trick. Switching back to my insane ones![]()
Code: Select all
info --file=gcc --node="Optimize Options"Code: Select all
--make-my-system-teh-l33t 
Sounds like your configuration is screwy. Make a backup of your ~/.e directory and thenlinerminator wrote:how does one go about protecting the system and minimizing any damage that may occur?
Code: Select all
rm -rf ~/.e/e/configThose CFLAGS will definately get you a broken system, not just E17. As for IBar, yes, it's just an application launcher - it doesn't function as a taskbar at all. Try loading the IBox module instead.Cinder6 wrote: maybe I should tone down my CFLAGS/LDFLAGS...
CFLAGS="-O3 -march=athlon64 -pipe -fomit-frame-pointer -momit-leaf-frame-pointer -ftracer -fforce-addr"
LDFLAGS="-Wl,-O1 -Wl,--sort-common -z combreloc -Wl,--enable-new-dtags"
I will try some saner CFLAGS right now.
EDIT: The one thing that will probably keep me from using E17 as a default is it doesn't tell me what the current operation is on my aterm, like xfce does. Nice to have it say emerge progress in the title bar (like "emerging package 1/25").
EDIT2: Well, conservative CFLAGS didn't do the trick. Switching back to my insane ones
EDIT3: Heh, now my terminal has the emerge stats on the title bar...weird. Anyways..
How come when I minimize a window (iconify), it doesn't show up on iBar? I have to go to the main menu (left-click), Windows option, and check the one I want to restore. Working as intended?

thanks for the tip - unfortunately no luck. now the thing segfaults every time i fire up anything...JoeG wrote: Sounds like your configuration is screwy. Make a backup of your ~/.e directory and thenexit enlightenment and log back in.Code: Select all
rm -rf ~/.e/e/config
Thanks, I will look into iBox. As for my CFLAGS, I guess I could ditch -ftracer and -fforce-addrvrln wrote:Those CFLAGS will definately get you a broken system, not just E17. As for IBar, yes, it's just an application launcher - it doesn't function as a taskbar at all. Try loading the IBox module instead.Cinder6 wrote: maybe I should tone down my CFLAGS/LDFLAGS...
CFLAGS="-O3 -march=athlon64 -pipe -fomit-frame-pointer -momit-leaf-frame-pointer -ftracer -fforce-addr"
LDFLAGS="-Wl,-O1 -Wl,--sort-common -z combreloc -Wl,--enable-new-dtags"
I will try some saner CFLAGS right now.
EDIT: The one thing that will probably keep me from using E17 as a default is it doesn't tell me what the current operation is on my aterm, like xfce does. Nice to have it say emerge progress in the title bar (like "emerging package 1/25").
EDIT2: Well, conservative CFLAGS didn't do the trick. Switching back to my insane ones
EDIT3: Heh, now my terminal has the emerge stats on the title bar...weird. Anyways..
How come when I minimize a window (iconify), it doesn't show up on iBar? I have to go to the main menu (left-click), Windows option, and check the one I want to restore. Working as intended?
I have an x86 system with those two flags in my CFLAGS, but I have never faced any problems. I think it is probably your LDFLAGS which are giving you those problems. ( I might be very wrong though. )Cinder6 wrote:Thanks, I will look into iBox. As for my CFLAGS, I guess I could ditch -ftracer and -fforce-addr
Have you updated from CVS with saner CFLAGS (perhaps with only -O2 -march=athlon64)? CVS is updated pretty often, so maybe....linerminator wrote:thanks for the tip - unfortunately no luck. now the thing segfaults every time i fire up anything...JoeG wrote: Sounds like your configuration is screwy. Make a backup of your ~/.e directory and thenexit enlightenment and log back in.Code: Select all
rm -rf ~/.e/e/config