> > At this point I do the patches or substitute files as required by the > > developers, then... > > > > ebuild compile > > ebuild install > > Does this look correct? I had sort of pieced this back together from > > man ebuild, but I've had a couple of issues over the last few days: > > [snip] > > You need to specify the ebuild as the second parameter as in the > previous steps.
Yes! Just my typing in and forgetting to type that. Now that you point out the ebuild package merge command, it appears from the ebuild man page that maybe the right order for me would be: ebuild package fetch ebuild package unpack do my edits ebuild package compile ebuild package install ebuild package qmerge This seems to be what the ebuild merge option is doing. Maybe you are suggestion that I can still use ebuild merge after the edits, which would possibly start from the compile step and go forward, but I'm hesitant to trust that with my limited knowledge of these tools and how to check things out. I'll give this a try. Thanks very much! Cheers, Mark > And note that install will do the "make install" step > (or whatever the package uses to install) in $DESTDIR, which is at > /var/tmp/portage/<package>/image. To really install the package you need > the merge step for ebuild, as in "ebuild <package.ebuild> merge", this > will copy the content of $DESTDIR to the live filesystem. > > Marius > > -- > [EMAIL PROTECTED] mailing list > > -- [EMAIL PROTECTED] mailing list
