public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Chad M. Huneycutt" <chad.huneycutt@acm.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Problem With TeX and opencm
Date: Mon, 08 Jul 2002 19:55:25 -0400	[thread overview]
Message-ID: <3D2A266D.9010806@acm.org> (raw)
In-Reply-To: 1026170178.4258.6.camel@mango

Mark Cox wrote:
> On Tue, 2002-07-09 at 00:25, Chad M. Huneycutt wrote:
> 
>>Mark Cox wrote:
>>
>>>opencm (www.opencm.org) wants to generate ps documents from info files
>>>when you tell it to compile. The problem is sandbox (I think it is this
>>>that denies access to everything outside of the work dir..someone
>>>correct if it isn't.) causes this to happen .
>>>
>>>
>>>dvips -t letter opencm.dvi -o tmp.ps
>>>This is dvips(k) 5.86 Copyright 1999 Radical Eye Software
>>>(www.radicaleye.com)
>>>' TeX output 2002.07.08:1220' -> tmp.ps
>>>kpathsea: Running mktexpk --mfmode ljfour --bdpi 600 --mag 1+437/600
>>>--dpi 1037 cmbx12
>>>ACCESS DENIED  mkdir:     /usr/share/texmf/fonts/pk
>>>mkdir: cannot create directory `/usr/share/texmf/fonts/pk': Permission
>>>denied
>>
>>
>>Is this an ebuild you are testing, or is this one in portage?  The first 
>>line up there needs to be removed from the install process.  It might 
>>possibly be moved to another section of the ebuild, or just removed 
>>completely.  If this is in portage, then if no bug exists on 
>>bugs.gentoo.org, please submit one.  If you really want to install it over 
>>the sandbox violation, then do
>>
>># FEATURES="-sandbox" ebuild ...
> 
> 
> Sorry I always I leave something important out.... Yes this is an ebuild
> I'm testing. And no it isn't in the portage repository either.
> 
> I like the idea of sandbox as I don't trust the program (or any program)
> to be 100% correct (especially in an alpha release). 
> 
> Is this a bug in portage I don't think so. Maybe sandbox may have to
> make exceptions for TeX, or is there a way for TeX to all of these
> metafonts (if thats what its trying to create ??) when you emerge TeX.

One solution would be to remove this from the install process and put it in 
the config step.  The config step happens after merge, so the sandbox 
checking is no longer in effect.

You might also check the tetex ebuild and see what kind of tricks they do 
there.



-- 
Chad Huneycutt (chadh@gentoo.org)



  reply	other threads:[~2002-07-08 23:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-08  2:47 [gentoo-dev] Problem With TeX and opencm Mark Cox
2002-07-08  1:49 ` Matthew Kennedy
2002-07-08  3:17   ` Mark Cox
2002-07-08 14:25 ` Chad M. Huneycutt
2002-07-08 23:16   ` Mark Cox
2002-07-08 23:55     ` Chad M. Huneycutt [this message]
2002-07-09 22:37 ` Pierre-Henri Jondot
2002-07-10  0:31   ` Mark Cox
2002-07-10  5:52     ` Matthew Kennedy
2002-07-10  6:33       ` Pierre-Henri Jondot
2002-07-10 13:01       ` Chad M. Huneycutt
2002-07-10 18:09         ` Matthew Kennedy
2002-07-10 18:13           ` Chad Huneycutt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3D2A266D.9010806@acm.org \
    --to=chad.huneycutt@acm.org \
    --cc=chadh@cc.gatech.edu \
    --cc=gentoo-dev@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox