Ebuild basics

[NU-Slacker]

Hey all. I have finally decided that its time to start making ebuilds for a lot of the programs that I like to have around. I just made my first ebuild earlier today and after a little bit of confusion I have finally got it to download and compile without problems. However, when it comes time to install, sandbox violations pop up everywhere.

I am currently using the package's 'make install' to try and get it installed. Is there something Im missing. Is this a fault with the developer's make or my ebuild? Is there a more proper way to install a package? Any hints?
_________________
"There are 10 types of people: those that understand binary and those who dont."

[kutsuya]

[lx]

/usr/lib/portage/ebuild.sh contains the function einstall, you can use this function in your ebuild it's shorthand for make prefix=${D}/usr mandir=.... etc etc etc.
Many packages have a special variable for install something like DESTDIR in this case you can do make DESTDIR=${D} install, check the main Makefile for such a variable or else use einstall, what ever works for you,

Cya lX.
_________________
"Remember there's a big difference between kneeling down and bending over.", Frank Zappa

[NU-Slacker]

Thanks for your help. I figured it was probably a problem with me specifying a path incorrectly somewhere, and you guys helped me find the problem. Now Ive just got to take care of some other annoying issues and I should be good to go.

Thanks for the help.
_________________
"There are 10 types of people: those that understand binary and those who dont."

[phong]

If you think your ebuild might be useful for others, please don't forget to share it on bugs.gentoo.org. It may get included in the official portage tree.
_________________
"An empty head is not really empty; it is stuffed with rubbish. Hence the difficulty of forcing anything into an empty head."
-- Eric Hoffer

[sarnold]

[Pythonhead]