[gentoo-soc] Ebuild generator week 4 update

[Sebastian Parborg]

This week I've come really close to generate a actual ebuild for the
"doneyet" project.
So soon my ebuild generator will actually generate ebuild and not just
gather information about the packages.

I've managed to solve the problem I've had last week with how I should
store the information that I get from the makefiles. At first I
thought that it would be good to have a huge list with all the targets
-> dependencies linked so that it would have a tree structure. But
after I've made some prototypes I thought that it would be to
cumbersome so instead I create multiple lists with (kinda like the
structure in the makefile itself) so that I can link them when needed
and get access to all the deps and targets without having to search a
huge tree list.
To figure out what files I need to search for includes I look at the
first target list (they are ordered in the order they are in the
makefile), because it is the one that would be built when you just
type "make", and then search for any *.o targets and return all files
that the .o file target depends on.

This also caused me to implement the first "try catch exception" in my
program as files listed in the makefile might not exist. I didn't know
makefiles allowed this...
Anyhow, after that was done I implemented a .h file -> package
"converter" with the help of qfile. I will change this later as you
have to have all the deps for the program installed otherwise qfile is
useless.
Now I have begun working on the ebuild text output so I can finally
put the information to use.
I think I will make it to the deadline of my next milestone as I think
I'm quite close right now.

I would also like to have some input on a few things:
1. I would like my generator to be able to download the source archive
for the project so you don't have to fill out the URL in the
ebuildfile manually and for ease of use. But where should I download
the unpack the files? I first thought that I should do it like portage
and save the archive in distfile and unpack in where portage usually
does. However to do this you have to be root and I don't know if it's
a good idea or not.

2. How do I handle makefile projects that doesn't have an "install"
target? For the doneyet project you only need to installed the
compiled binary so I can just do "doexe" but I realize that you can't
take that for granted.

3. Should I look for RDEPEND deps?

Next week I plan to finish the "make, make install" project support,
but I need more projects to test things out on so I know that I
haven't overlooked anything! So if you have any "good and simple"
makefile project please post them here.