[gentoo-dev] How does ebuild move files to the final destination

[Brett I. Holcomb]

I'm working on an ebuild for getting a program for cvs and have some 
questions.  The ebuild succesfully fetchs, unpacks, and compiles the cvs 
source but I'm puzzled on some aspects of src_install.

I notice that the make install command references ${D} as in 
prefix=${D}/somedir or mandir=${D}/usr/share/man.  However ${D} is 
essentially a temporary directory (${PORTAGE_TMPDIR}/PORTAGE/${PF}/image) 
which is used to construct the directory structure of the program as it will 
be after it's installed to /usr or wherever.  In short, the entire program 
install with all it's directory is built under ${D}.

After looking at the emake and other eclass functions I can not see where the 
tree in ${D} is moved to the final location (say /usr/someprog from 
${D}/usr/someprog) but it obviously happens <G>!  Is there some portage code 
somewhere that does the move?  How does the move happen and when? 

The reason for this is that the program I have doesn't have a make install  - 
I tried using egamesinstall and all that got created were some executables in 
/usr/games/bin - nothing got moved to /usr/games/programname.  This makes 
sense because if I download cvs by hand and follow the ./autogen.sh, 
./configure, make process in the program install docs then the entire program 
is built under what ever directory I put the two cvs modules in.

Thank you.

-- 

Brett I. Holcomb
AKA Grunt <><

--
gentoo-dev@g.o mailing list