| 1 |
On Monday 30 October 2006 19:57, Francesco Talamona wrote: |
| 2 |
> On Saturday 28 October 2006 11:08, Hemmann, Volker Armin wrote: |
| 3 |
> > On Saturday 28 October 2006 07:02, Duncan wrote: |
| 4 |
> > > You /could/ try turning sandbox off (in FEATURES). That's a bit |
| 5 |
> > > dangerous by itself, but if you turn userpriv on at the same time, |
| 6 |
> > > it should be fairly safe. |
| 7 |
> > |
| 8 |
> > NO! |
| 9 |
> > |
| 10 |
> > Just no! |
| 11 |
> > |
| 12 |
> > Never ever turn of sandbox. Without sandbox, files can end everywhere |
| 13 |
> > in your installation, destroying stuff, make apps segfault randomly - |
| 14 |
> > and the worst, portage does not know about them. |
| 15 |
> > |
| 16 |
> > Never ever turn of sandbox. And never tell others to do so. |
| 17 |
> > btw |
| 18 |
> > * sys-devel/gcc |
| 19 |
> > Latest version available: 4.1.1-r1 |
| 20 |
> > Latest version installed: 4.1.1-r1 |
| 21 |
> > |
| 22 |
> > and I have sandbox enabled. So it is not a sandbox problem. Something |
| 23 |
> > else is broken on his system. |
| 24 |
> |
| 25 |
> I'm running -sandbox since 09-June-2005, am I in such a danger? |
| 26 |
> Shouldn't I have experienced destructive issues in the meantime? |
| 27 |
> FEATURES="candy ccache buildpkg fixpackages -sandbox" |
| 28 |
> |
| 29 |
|
| 30 |
you have experienced it. You just don't see it. Somewhere in your filesystem |
| 31 |
are files, that should not be there. Files, that portage does not know about |
| 32 |
and that won't be removed, when the package gets uninstalled. |
| 33 |
|
| 34 |
If a package does not build with sandbox, it is broken. Open a bug. |
| 35 |
-- |
| 36 |
gentoo-amd64@g.o mailing list |
Archives