Norberto Bensa schreef: > Holly Bostick wrote: > >> Norberto Bensa schreef: >> >>> sudo ebuild ./kbfx-0.4.8beta.ebuild digest >>> >>> I get: >>> >>> Appending /usr/local/portage to PORTDIR_OVERLAY... !!! >>> /usr/local/portage does not seem to have a valid PORTDIR >>> structure. >> >> So I would first suggest that you make sure your ebuild is >> correctly placed in the correct tree structure, and then I would >> digest it by full path, rather than from within the directory, as >> you seem to be doing. >> > > > [EMAIL PROTECTED] /usr/local/portage/kde-misc/kbfx $ sudo ebuild > /usr/local/portage/kde-misc/kbfx/kbfx-0.4.8beta.ebuild digest > Password: Appending /usr/local/portage to PORTDIR_OVERLAY... !!! > /usr/local/portage does not seem to have a valid PORTDIR structure. > > > $ grep OVERLAY /etc/make.conf PORTDIR_OVERLAY=/usr/local/portage > > > I don't know. Perhaps one of those (stupid) security settings > somewhere for latest portage :( > > Thank you Holly and Rumen. >
Now, now; not so hasty.... what I notice is that this is a *very* explicit error message. So if we assume that it means exactly what it says, where does that get us? /usr/local/portage does not seem to have a valid PORTDIR structure very clearly says that the overlay must have a structure identical to PORTDIR; your portdir *is* /usr/portage, is it not? Assuming that it is, then you have replicated this structure in /usr/local/portage for this ebuild-- but there are three possible holes in this 'theory' such as it is. One is that you are trying to digest the ebuild from within the directory, rather than from, say, /usr/local. It is remotely possible that this is not a good idea, since the overlay tree should possibly not be the current working directory (as I suggested before). Second is that you're using sudo. I find many anomolies in sudo; mostly revolving around it not being a 'real' login shell, but some kind of weird spawned shell process that doesn't necessarily transfer all variables and/or permissions, depending on settings. You might try again, using su - -c instead of sudo to get root privileges. Third is that there's a problem with your ebuild, which also uses the PORTDIR variable. It is possilbe that your ebuild is incorrectly using this variable and not using a 'valid' PORTDIR. I'm not much of an ebuild writer, but you might want to go over it with a fine-toothed comb to make sure that this error isn't reporting an anomaly in the ebuild it's trying to read, rather than Portage, and is just poorly expressing that (it happens). HTH, Holly -- gentoo-user@gentoo.org mailing list
