From Gentoo Linux Wiki

[edit] Overhaul

Given the major overhaul this article has undergone, i've cleared this page, as what it discussed is outdated.

Rollback and correct at your discretion. Ni1s 22:25, 21 September 2006 (UTC)

[edit] Article Title

This is not that important, but the name HOWTO e17 is not, in my oppinion, that great. It should also indicate that everything is pulled from CVS. Alternatives would be something like:

HOWTO Enlightenment DR17

HOWTO E17 from CVS

HOWTO e17 works as long as you already know what it refers too. Ni1s 22:31, 21 September 2006 (UTC)

[edit] Cleanup & Wikify

About the {{wikify}} & {{cleanup}}, why and where? A simple "I don't understand foo." or "What gives with bar?!" would really help. Ni1s 18:17, 13 November 2006 (UTC)

[edit] EFL Software Details

Hi, a while back we removed the applications list wouldn't it be nice to have at least a link to a central place that tries to explain what they are/do

http://www0.get-e.org/Resources/Applications/ or the modules in CVS:

steve@vaion ~/work/e $ ls e_modules/ AUTHORS README.BROKEN calendar deskshow emu flame mem mount rss taskbar winselector CVS alarm configure.in devian engage language mixer net screenshot tclock wlan Makefile.in autogen.sh cpu e_modules-TEMPLATE.spec.in eveil mail monitor photo slideshow uptime README bling debian e_modules.spec evolume mbar moon rain snow weather

cheers,

Steve

There are no such thing as "e17 software" except e17 itself. Apps like Emphasis and ephoto are ETK and EWL apps. The purpose of this article is E17, the window manager, and nothing else. Hence the title HOWTO e17. But sure, an article about ETK,EWL and the appies based on them would be cool. And maybe the e_modules should get a article too, but then again, we might end up writing stuff noone will ever read... Ni1s 17:50, 13 November 2006 (UTC)

[edit] The Enlightenment Overlay

Could someone wikify the instructions for setting up and using Vapier's new overlay? This wiki article mentions the use of the overlay and the decision between snapshots and live CVS but doesn't provide instructions for either. --59.167.57.240 05:55, 20 January 2007 (UTC)

Some instructions have been added, but the article should get some more overall fiddling now that the overlay supplies snapshot ebuilds. Ni1s 11:46, 24 January 2007 (UTC)

Also, CVS updates are now easier, like -- emerge -av1 `eix --only-names -J --in-overlay /usr/portage/local/layman/enlightenment`

[edit] Ecore is Missing in E17_EBUILDS_TO_INSTALL ???

Can someone clarify for me or correct the list of packages need for E17_EBUILDS_TO_INSTALL. x11-libs/ecore is missing as I see in the install script on bottom or is this affected?

[edit] Ecore USE flags and examine compile errors

Just tried to emerge e17, mostly worked. Problems encountered, something included ecore refused to compile without ecore compiled with the dbus flag (and dbus installed). Added flag and remerge fixed that. After that, examine refused to compile complaining about missing some ecore_ipc deps (wich are provided by ecore). I had to manually invoke ebuild compile, wich will still complain about ecore_ipc when executing

gcc -g -O2 -I/usr/include/ewl -I/usr/include/libpng12 -g -O2 -o exsh exsh.o ecore_config_client.o -lreadline /usr/lib/libecore.so -ldl -lpthread -lm

Since I'm not exactly sure how to fix the automake env, I just fixed the cmd line. The correct line should use libecore_ipc.so and NOT just libecore.so. It now looks like that :

gcc -g -O2 -I/usr/include/ewl -I/usr/include/libpng12 -g -O2 -o exsh exsh.o ecore_config_client.o -lreadline /usr/lib/libecore_ipc.so -ldl -lpthread -lm

Now make sure everything got its make (make in the ./configure dir). Then you're ready for ebuild install and ebuild qmerge. Not particularly great fix, but it's a fix nonetheless. Engage still doesn't compile, as e_utils, there's a problem with the autoconf env. @EVAS_CFLAGS@ and @ECORE_CFLAGS@ are not being replaced, and then used directly in the compile line, resulting in file not found. Anyone had success with engage lately? My current status : e17 segfault at start. i'm working on that. Resolved. In fact, it always worked! I was trying to get it to work on VNC from the start, so I didn't noticed it run just fine locally, but segfaulted when started via xinetd and xvnc.

A note to those wanting to get E17 to work via Xvnc, the color depth MUST be set to 24!

[edit] Keywords

I notified some problems with keywords, I tried to unmask these packages, but it still wont install (tested on portage and paludis).

Overlay instruciontions and keywording have been rewriten.Ni1s 11:53, 29 May 2007 (UTC)

[edit] New helper script

Hi. I have written in Python a new helper script for managing the e17 keybindings. The advantage is that it has 32 lines instead of 134 like the shell script. It is far simpler and more readable. This means that it can be more easily reviewed and inspected for bugs.

Here it is:

#!/usr/bin/python

from sys import argv, exit # import "argv" (which has the command line arguments) and "exit" from the "sys" module.
from os import system # import the "system" function from the "os" module. This function executes commands.
if len(argv) == 1:
    exit('You must specify at least one command line argument. Try %s --help' %argv[0])
elif argv[1] == '-h' or '--help'.startswith(argv[1]):
    print 'This is a helper script for managing keybindings in e17.\n'
    print '%-40s delete all keybindings listed in FILE'  %(argv[0] + ' del FILE')
    print '%-40s add all keybindings listed in FILE' %(argv[0] + ' add FILE')
    print '%-40s save the keybindings to FILE, by copying the output of the command "enlightenment_remote -binding-key-list" to FILE\n' % (argv[0] + ' save FILE')
    print 'For the "del" and "add" commands, FILE should be in the same format of the file created by the "save" command; for convenience, blank lines in FILE are ignored'
elif argv[1] in ('add', 'del'):
    bindingsf = file(argv[2]) # open file named argv[2] in the default mode of "read"
    bindingsf.readline() # Read the first line and do nothing with it, thus discarding it
    import re # import "re" module (for regular expressions)
    delim = re.compile('\\s*\\w+=') #now delim is the compiled regular expression from "\\s*\\w+=". This pattern matches 0 or more whitespace characters followed by 1 or more alphanumeric characters followed by a "=". This delimits the relevant fields in the output of enlightenment_remote -binding-key-list
    relevantlines = [line for line in bindingsf if line != '' and not line.isspace() and 'REPLY <- END' not in line]
    for fields in [delim.split(line) for line in relevantlines]:
        fields[0] = ' ' # Replace first field - which is garbage - with a space
        command = 'enlightenment_remote -binding-key-' + argv[1] + ' '.join(fields).replace('|','\\|')
        print command,
        ret = system(command)
        if ret != 0:
            exit ("Error. Command returned %d. Exitting. " %ret)
    print "%d keybindings processed" %len(relevantlines)
elif argv[1] == 'save':
    system('[ -e "%s" ] && echo File "%s" exists. I refuse to overwrite. ||\
enlightenment_remote -binding-key-list > %s' %(argv[2], argv[2], argv[2]))
else:
    exit('Unrecognized argument %s. Try %s --help' %(argv[1], argv[0]))

Jorgepeixoto 20:21, 7 August 2007 (UTC)

[edit] How to set up _EBUILDS= for updates ?

Here are a few examples of how to list installed ebuilds that we may want to update.

Permissive way:

qlist -I -v |grep "\-9999"

restricted way

qlist -I -C -v dev-db/ dev-libs/ x11-libs/ dev-libs/ media-libs/ x11-wm/ |grep "\-9999"

so, we may end up with:

export _EBUILDS=`qlist -I -C -v |grep "\-9999" | xargs echo "" | sed 's/ / =/g' `
echo $_EBUILDS