Re: [gentoo-dev] ebuild failing with sandbox violation

Re: [gentoo-dev] ebuild failing with sandbox violation

[Avi Schwartz]

In my very short ebuild experience, I have seen these sandbox violations
in two cases:

1) If I forgot to add the ${D} prefix to the directory specifications in
src_install() or did not set DESTDIR properly.

2) The program's Makefile ignores ${DESTDIR}.  This is quite common when
/etc is involved.  If you will take a look at the dev-db/unixODBC
ebuild, you will see that the Makefile.in is modified to add ${DESTDIR}
in front of the /etc directory to fix this.

Avi

On Mon, 2002-04-29 at 12:19, jurquijo@nyso.org wrote:
> Can anyone point me to a doc or mailing list post that describes sandbox
> violations?
> 
> I've written an ebuild for imwheel and it used to work/install fine on a
> gentoo rc6 system I had installed.
> 
> Trying to install the same ebuild on a recently built system fails with a
> "sandbox violation" when the ebuild tries to create /etc/imwheelrc.
> 
> I thought that in all steps prior to the "merge" command, ebuilds were
> built in a "safe" temporary environment before being copied to the live
> filesystem.
-- 
Avi Schwartz
avi@CFFtechnologies.com

[gentoo-dev] ebuild failing with sandbox violation

[jurquijo]

Can anyone point me to a doc or mailing list post that describes sandbox
violations?

I've written an ebuild for imwheel and it used to work/install fine on a
gentoo rc6 system I had installed.

Trying to install the same ebuild on a recently built system fails with a
"sandbox violation" when the ebuild tries to create /etc/imwheelrc.

I thought that in all steps prior to the "merge" command, ebuilds were
built in a "safe" temporary environment before being copied to the live
filesystem.

Has something changed radically in emerge/ebuild?

TIA,
Julian