This is my edited version of Jeff Hoogland's original article on the eet command. It is posted here because it is hard to find online as the original link is now dead and not even found in the Wayback Machine.
One of the things that allow the Enlightenment Foundation Libraries to be as fast and efficient as they are in their use of compiled files for storing information. While these compiled files are fast, the drawback to using them is that there is some difficulty when you want to manually access/edit the data these files contain. Today I am going to talk about how we can gain access to the data contained in compiled Enlightenment Foundation Library EET data files.
EET files are binary data files that generally hold configuration options/settings for applications. To work with these files we will need access to the eet command contained in the Enlightenment Foundation Libraries - which you can generally install through your Linux distribution’s package manager or you can compile them from the source code.
The first thing we need to do is decompile the EET file. We do this using the eet command as follows:
eet -d myfile.eet config myoutput.txt
Where myfile.eet is the EET file you wish to decompile and myoutput.txt is where you want the data decompiled to be placed. For example, if the file we wanted to decompile was called e.cfg we would run:
eet -d e.cfg config e.txt
This would result in a file called e.txt with your data in it.
Once you make any changes you need to make to the decompiled data we can turn it back into a compiled EET file again using the eet command:
eet -e newfile.eet config mydata.txt 1
So for example, if we wanted to recompile the e.txt that we created previously, we would run:
eet -e e2.cfg config e.txt 1
Which would recompile our changes into a new EET file called e2.cfg. Hopefully, this will save some folks some headaches when it comes to figuring out how to manually manipulate EET using the command line - a process that is not very well documented.
Cheers,
~Jeff Hoogland
December 7, 2017