On Tue, 29 Aug 2006, Markus Dittrich wrote: > On Wed, 30 Aug 2006, Andrey G. Grozin wrote: > > 1. Some ebuild (usually with the USE flag "doc") starts latex > > 2. Some font used in the latex file has not yet been used on this > > particular computer > > 3. latex starts metafont to generate this font > > 4. metafont wants to write it to /var/cache/fonts > > 5. This triggers sandbox violation > Have a look at [1] and the links therein which provide some info on how to > work with the sandbox. Keep in mind, though, that these commands should only > be used if there really is no other way > (such as patching the makefile etc.) to get rid of the > sandbox violations; the sandbox is present for a very good reason! > An ebuild in portage that shows these commands in action would be > app-text/ptex-3.1.8.1_p20050418 Thanks for the pointer. I think I've fixed the immediate problem.
But I got such sandbox violations when emerging packages from the main portage tree more than once. Many packages use LaTeX for documentation; metafont can be called at any moment. Shouldn't the directories to which it writes generated fonts be added to SANDBOX_WRITE globally? Then the level of users' frustration would be lower. Andrey -- [email protected] mailing list
