On Wed, Apr 2, 2014 at 5:58 AM, Jonathan Callen <[email protected]> wrote:
> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > > On 04/01/2014 10:03 AM, Kfir Lavi wrote: > > On Mon, Mar 31, 2014 at 11:53 PM, Duncan <[email protected]> wrote: > > > >> Alexandre Rostovtsev posted on Mon, 31 Mar 2014 14:54:09 -0400 as > excerpted: > >> > >>> The best solution is to figure out why the directory is being created > there and whether it > >>> is customizable. Maybe the code actually is creating > $HOME/InstallShield? Then export > >>> HOME=${T} in your ebuild. > >> > >> Well, "best" would be not to run software where the author doesn't > respect your rights to > >> study, patch and share the software, with or without those > modifications, in the first > >> place. > >> > >> But understanding not everybody is prepared to go that route and it's > their machines and > >> life, not mine... > >> > >> On the ebuild execution side, as a last resort you can turn off > FEATURES=sandbox and perhaps > >> FEATURES=userpriv as well, allowing it free access to do whatever it's > going to do. > >> > >> Alternatively and for both the ebuild creation and execution sides, > take a look at > >> /etc/sandbox.conf and the files in /etc/sandbox.d/, and grep SANDBOX_ in > >> $PORTDIR/*/*/*.ebuild and $PORTDIR/eclass/*.eclass. > >> > >> (Tho it's not always proprietaryware; take a look at emacs... based on > some of the other > >> packages that disable sandbox, I'd guess it's the lisp.) > >> > >> Anyway, SANDBOX_PREDICT or SANDBOX_WRITE will probably do it in your > case (violations not > >> flat-out-segfaults as emacs apparently triggers), but SANDBOX_ON=0 is > there if you REALLY > >> need it. > >> > >> Tho obviously if you were doing that ebuild for the main tree, any > messing with sandbox isn't > >> going to get it there any faster. But if you're doing it for your own > (including possibly > >> company internal) use only... > >> > >> -- Duncan - List replies preferred. No HTML msgs. "Every nonfree > program has a lord, a > >> master -- and if you use the program, he is your master." Richard > Stallman > >> > >> > >> > > Thanks Duncan, > > > > addwrite /root/InstallShield addwrite /etc/mtab > > > > did the trick. > > > > Thanks all for replaying. > > > > Kfir > > > > IIRC, you really should use `addpredict` instead of `addwrite`, as you > don't want the package > *really* writing to those locations. > I have tried it, but the installation does not work. Matlab does not really install itself, as it throws a lot of NullPointerException. What I'm doing is letting it write using addwrite and then at the post install I delete this directory. What I don't understand is, why it needs to get write permissions to /etc/mtab ? > - -- > Jonathan Callen > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.22 (GNU/Linux) > Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ > > iQIcBAEBCgAGBQJTO3zXAAoJELHSF2kinlg4emwQAJNwluWdrGXrBMj3f+j4Sx8+ > Ch6M5FF5lRqQXnnqZUvXrEd2t6iBMrZ0Xm/AVnAkCNr4vlpRdcS7ahmbCSC4jT2f > Plct5CG6+3/W1PbNfmSLoBxIlEU8vMzx4gUJtaGUOuuekjuYK+xKHjlskVJks0Y8 > im0k/1VDR13J6NyneBmISH0SglmYmVTAezT9yngqm089cfi4DkZo4MdR/r4TUtRd > lu62NlZ517t2pNINJe5anRq9Q0D+obGg8gmZ0+C2jNwj+9thXZWnSLuV03eXpIG3 > ntVaVRI2H4p9hPWQJMCfVsyVfudYDiP/05hOkeTOd3NV+8crODoY06CQNhZ7e0hb > yB+TE+bqufAuqaEalhEB5oxn61u+ALYHCXSRNjuQItzZrWRSXqV6r7Hd9TKtHEL0 > w+ayThJYXqWDSj69yXpyHMldWovydKMVv7Goz9gdzBjPIRVfLZoUmvpl1RGwsOII > ahubgQPp2n0cibm0K2Uaqr1xg7MuvUr810hl/LVhK8OlsT3gqDgMXyZrG6S1x/jo > DV7qCJCqy5GjDc4KdS/tPTXJt9krAjRNDIxfA/jzvOC8lghZuAFFZpUSHfBR9XL+ > VUMUwhwdathtQic20+t4vnXP24AetYvqaO7K1dRFJhopGE8P0gnt7r8xQa5uZSkr > QtKhDStXVcLkOnuw3jy+ > =3dEf > -----END PGP SIGNATURE----- > >
