Re: [gentoo-dev] Problem With TeX and opencm

Re: [gentoo-dev] Problem With TeX and opencm

[Matthew Kennedy]

Do you have sandbox in /etc/ld.so.preload? If so, try deleting 
/etc/ld.so.preload


On Sun, 2002-07-07 at 21:47, 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
> kpsestat: /usr/share/texmf/fonts/pk/..: No such file or directory
> chmod: too few arguments
> Try `chmod --help' for more information.
> ACCESS DENIED  mkdir:     /usr/share/texmf/fonts/pk/ljfour
> mkdir: cannot create directory `/usr/share/texmf/fonts/pk/ljfour':
> Permission denied
> kpsestat: /usr/share/texmf/fonts/pk/ljfour/..: No such file or directory
> chmod: too few arguments
> Try `chmod --help' for more information.
> ACCESS DENIED  mkdir:     /usr/share/texmf/fonts/pk/ljfour/public
> mkdir: cannot create directory
> `/usr/share/texmf/fonts/pk/ljfour/public': Permission denied
> kpsestat: /usr/share/texmf/fonts/pk/ljfour/public/..: No such file or
> directory
> chmod: too few arguments
> Try `chmod --help' for more information.
> ACCESS DENIED  mkdir:     /usr/share/texmf/fonts/pk/ljfour/public/cm
> mkdir: cannot create directory
> `/usr/share/texmf/fonts/pk/ljfour/public/cm': Permission denied
> kpsestat: /usr/share/texmf/fonts/pk/ljfour/public/cm/..: No such file or
> directory
> chmod: too few arguments
> Try `chmod --help' for more information.
> mktexpk: mktexdir /usr/share/texmf/fonts/pk/ljfour/public/cm failed.
> kpathsea: Appending font creation commands to missfont.log.
> dvips: Font cmbx12 not found, characters will be left blank.
> 
> This is repeated for every font it uses. Giving this in the missfont.log
> file.
> 
> mktexpk --mfmode ljfour --bdpi 600 --mag 1+437/600 --dpi 1037 cmbx12
> mktexpk --mfmode ljfour --bdpi 600 --mag 1+120/600 --dpi 720 cmbx12
> mktexpk --mfmode ljfour --bdpi 600 --mag 1+57/600 --dpi 657 cmr10
> mktexpk --mfmode ljfour --bdpi 600 --mag 1+57/600 --dpi 657 cmsy10
> mktexpk --mfmode ljfour --bdpi 600 --mag 1+264/600 --dpi 864 cmbx12
> mktexpk --mfmode ljfour --bdpi 600 --mag 1+0/600 --dpi 600 cmr12
> mktexpk --mfmode ljfour --bdpi 600 --mag 1+264/600 --dpi 864 cmbxti10
> mktexpk --mfmode ljfour --bdpi 600 --mag 1+57/600 --dpi 657 cmti10
> mktexpk --mfmode ljfour --bdpi 600 --mag 1+57/600 --dpi 657 cmtt10
> mktexpk --mfmode ljfour --bdpi 600 --mag 1+57/600 --dpi 657 cmsl10
> mktexpk --mfmode ljfour --bdpi 600 --mag 1+57/600 --dpi 657 cmbx12
> mktexpk --mfmode ljfour --bdpi 600 --mag 1+57/600 --dpi 657 cmsltt10
> mktexpk --mfmode ljfour --bdpi 600 --mag 1+57/600 --dpi 657 cmb10
> mktexpk --mfmode ljfour --bdpi 600 --mag 1+0/600 --dpi 600 cmr7
> mktexpk --mfmode ljfour --bdpi 600 --mag 1+0/600 --dpi 600 cmr9
> mktexpk --mfmode ljfour --bdpi 600 --mag 1+0/600 --dpi 600 cmti9
> mktexpk --mfmode ljfour --bdpi 600 --mag 1+0/600 --dpi 600 cmtt9
> 
> Does anyone know how to fix this ??
> 
> Mark Cox
> 
> 
> 
> 
> 
> 
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev
-- 
Matthew Kennedy
Gentoo Linux Developer

[gentoo-dev] Problem With TeX and opencm

[Mark Cox]

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
kpsestat: /usr/share/texmf/fonts/pk/..: No such file or directory
chmod: too few arguments
Try `chmod --help' for more information.
ACCESS DENIED  mkdir:     /usr/share/texmf/fonts/pk/ljfour
mkdir: cannot create directory `/usr/share/texmf/fonts/pk/ljfour':
Permission denied
kpsestat: /usr/share/texmf/fonts/pk/ljfour/..: No such file or directory
chmod: too few arguments
Try `chmod --help' for more information.
ACCESS DENIED  mkdir:     /usr/share/texmf/fonts/pk/ljfour/public
mkdir: cannot create directory
`/usr/share/texmf/fonts/pk/ljfour/public': Permission denied
kpsestat: /usr/share/texmf/fonts/pk/ljfour/public/..: No such file or
directory
chmod: too few arguments
Try `chmod --help' for more information.
ACCESS DENIED  mkdir:     /usr/share/texmf/fonts/pk/ljfour/public/cm
mkdir: cannot create directory
`/usr/share/texmf/fonts/pk/ljfour/public/cm': Permission denied
kpsestat: /usr/share/texmf/fonts/pk/ljfour/public/cm/..: No such file or
directory
chmod: too few arguments
Try `chmod --help' for more information.
mktexpk: mktexdir /usr/share/texmf/fonts/pk/ljfour/public/cm failed.
kpathsea: Appending font creation commands to missfont.log.
dvips: Font cmbx12 not found, characters will be left blank.

This is repeated for every font it uses. Giving this in the missfont.log
file.

mktexpk --mfmode ljfour --bdpi 600 --mag 1+437/600 --dpi 1037 cmbx12
mktexpk --mfmode ljfour --bdpi 600 --mag 1+120/600 --dpi 720 cmbx12
mktexpk --mfmode ljfour --bdpi 600 --mag 1+57/600 --dpi 657 cmr10
mktexpk --mfmode ljfour --bdpi 600 --mag 1+57/600 --dpi 657 cmsy10
mktexpk --mfmode ljfour --bdpi 600 --mag 1+264/600 --dpi 864 cmbx12
mktexpk --mfmode ljfour --bdpi 600 --mag 1+0/600 --dpi 600 cmr12
mktexpk --mfmode ljfour --bdpi 600 --mag 1+264/600 --dpi 864 cmbxti10
mktexpk --mfmode ljfour --bdpi 600 --mag 1+57/600 --dpi 657 cmti10
mktexpk --mfmode ljfour --bdpi 600 --mag 1+57/600 --dpi 657 cmtt10
mktexpk --mfmode ljfour --bdpi 600 --mag 1+57/600 --dpi 657 cmsl10
mktexpk --mfmode ljfour --bdpi 600 --mag 1+57/600 --dpi 657 cmbx12
mktexpk --mfmode ljfour --bdpi 600 --mag 1+57/600 --dpi 657 cmsltt10
mktexpk --mfmode ljfour --bdpi 600 --mag 1+57/600 --dpi 657 cmb10
mktexpk --mfmode ljfour --bdpi 600 --mag 1+0/600 --dpi 600 cmr7
mktexpk --mfmode ljfour --bdpi 600 --mag 1+0/600 --dpi 600 cmr9
mktexpk --mfmode ljfour --bdpi 600 --mag 1+0/600 --dpi 600 cmti9
mktexpk --mfmode ljfour --bdpi 600 --mag 1+0/600 --dpi 600 cmtt9

Does anyone know how to fix this ??

Mark Cox

Re: [gentoo-dev] Problem With TeX and opencm

[Mark Cox]

Sorry I forgot this bit

I get the error after doing

ebuild opencm-0.1.0_alpha7-r2.ebuild compile 

so doesn't sandbox get called anyway.

On Mon, 2002-07-08 at 11:49, Matthew Kennedy wrote:
> Do you have sandbox in /etc/ld.so.preload? If so, try deleting 
> /etc/ld.so.preload
> 
> 
> On Sun, 2002-07-07 at 21:47, 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
> > kpsestat: /usr/share/texmf/fonts/pk/..: No such file or directory
> > chmod: too few arguments
> > Try `chmod --help' for more information.
> > ACCESS DENIED  mkdir:     /usr/share/texmf/fonts/pk/ljfour
> > mkdir: cannot create directory `/usr/share/texmf/fonts/pk/ljfour':
> > Permission denied
> > kpsestat: /usr/share/texmf/fonts/pk/ljfour/..: No such file or directory
> > chmod: too few arguments
> > Try `chmod --help' for more information.
> > ACCESS DENIED  mkdir:     /usr/share/texmf/fonts/pk/ljfour/public
> > mkdir: cannot create directory
> > `/usr/share/texmf/fonts/pk/ljfour/public': Permission denied
> > kpsestat: /usr/share/texmf/fonts/pk/ljfour/public/..: No such file or
> > directory
> > chmod: too few arguments
> > Try `chmod --help' for more information.
> > ACCESS DENIED  mkdir:     /usr/share/texmf/fonts/pk/ljfour/public/cm
> > mkdir: cannot create directory
> > `/usr/share/texmf/fonts/pk/ljfour/public/cm': Permission denied
> > kpsestat: /usr/share/texmf/fonts/pk/ljfour/public/cm/..: No such file or
> > directory
> > chmod: too few arguments
> > Try `chmod --help' for more information.
> > mktexpk: mktexdir /usr/share/texmf/fonts/pk/ljfour/public/cm failed.
> > kpathsea: Appending font creation commands to missfont.log.
> > dvips: Font cmbx12 not found, characters will be left blank.
> > 
> > This is repeated for every font it uses. Giving this in the missfont.log
> > file.
> > 
> > mktexpk --mfmode ljfour --bdpi 600 --mag 1+437/600 --dpi 1037 cmbx12
> > mktexpk --mfmode ljfour --bdpi 600 --mag 1+120/600 --dpi 720 cmbx12
> > mktexpk --mfmode ljfour --bdpi 600 --mag 1+57/600 --dpi 657 cmr10
> > mktexpk --mfmode ljfour --bdpi 600 --mag 1+57/600 --dpi 657 cmsy10
> > mktexpk --mfmode ljfour --bdpi 600 --mag 1+264/600 --dpi 864 cmbx12
> > mktexpk --mfmode ljfour --bdpi 600 --mag 1+0/600 --dpi 600 cmr12
> > mktexpk --mfmode ljfour --bdpi 600 --mag 1+264/600 --dpi 864 cmbxti10
> > mktexpk --mfmode ljfour --bdpi 600 --mag 1+57/600 --dpi 657 cmti10
> > mktexpk --mfmode ljfour --bdpi 600 --mag 1+57/600 --dpi 657 cmtt10
> > mktexpk --mfmode ljfour --bdpi 600 --mag 1+57/600 --dpi 657 cmsl10
> > mktexpk --mfmode ljfour --bdpi 600 --mag 1+57/600 --dpi 657 cmbx12
> > mktexpk --mfmode ljfour --bdpi 600 --mag 1+57/600 --dpi 657 cmsltt10
> > mktexpk --mfmode ljfour --bdpi 600 --mag 1+57/600 --dpi 657 cmb10
> > mktexpk --mfmode ljfour --bdpi 600 --mag 1+0/600 --dpi 600 cmr7
> > mktexpk --mfmode ljfour --bdpi 600 --mag 1+0/600 --dpi 600 cmr9
> > mktexpk --mfmode ljfour --bdpi 600 --mag 1+0/600 --dpi 600 cmti9
> > mktexpk --mfmode ljfour --bdpi 600 --mag 1+0/600 --dpi 600 cmtt9
> > 
> > Does anyone know how to fix this ??
> > 
> > Mark Cox
> > 
> > 
> > 
> > 
> > 
> > 
> > _______________________________________________
> > gentoo-dev mailing list
> > gentoo-dev@gentoo.org
> > http://lists.gentoo.org/mailman/listinfo/gentoo-dev
> -- 
> Matthew Kennedy
> Gentoo Linux Developer
> 

Re: [gentoo-dev] Problem With TeX and opencm

[Chad M. Huneycutt]

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 ...


-- 
Chad Huneycutt

Re: [gentoo-dev] Problem With TeX and opencm

[Mark Cox]

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.


> 
> 
> -- 
> Chad Huneycutt
> 
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev

Re: [gentoo-dev] Problem With TeX and opencm

[Chad M. Huneycutt]

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)

Re: [gentoo-dev] Problem With TeX and opencm

[Pierre-Henri Jondot]

On 08 Jul 2002 12:47:02 +1000
Mark Cox <coxhome@optushome.com.au> 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 .
> 
...
(sandbox violations due to pk's creation under /usr/share/texmf/fonts)

> Does anyone know how to fix this ??
> 
> Mark Cox
> 

I had exactly the same problem with pari-gp. (Well the problem didn't show
because I had already all the necessary pk's metafonted but I know it
might...)

A solution is, with tetex :
  set the env var USE_VARTEXFONTS to 1
  and the env var VARTEXFONTS to the directory where the fonts (metrics and
bitmaps) will be generated. Something like /var/tmp/portage/opencm???/work
perhaps will work... (Please correct me about the choice of this dir if I am
wrong.)

-- 
Pierre-Henri Jondot <Pierre-Henri.Jondot@wanadoo.fr>
Page perso : http://perso.wanadoo.fr/phj

Re: [gentoo-dev] Problem With TeX and opencm

[Mark Cox]

That worked like a charm.

All you have to do is put
export USE_VARTEXFONTS=1
export VARTEXFONTS=${WORKDIR}/fonts

and bingo it works.
I wonder who we should talk to to put this somewhere for other people who might
encounter the same problem.

Mark Cox

Pierre-Henri Jondot wrote:

> On 08 Jul 2002 12:47:02 +1000
> Mark Cox <coxhome@optushome.com.au> 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 .
> >
> ...
> (sandbox violations due to pk's creation under /usr/share/texmf/fonts)
>
> > Does anyone know how to fix this ??
> >
> > Mark Cox
> >
>
> I had exactly the same problem with pari-gp. (Well the problem didn't show
> because I had already all the necessary pk's metafonted but I know it
> might...)
>
> A solution is, with tetex :
>   set the env var USE_VARTEXFONTS to 1
>   and the env var VARTEXFONTS to the directory where the fonts (metrics and
> bitmaps) will be generated. Something like /var/tmp/portage/opencm???/work
> perhaps will work... (Please correct me about the choice of this dir if I am
> wrong.)
>
> --
> Pierre-Henri Jondot <Pierre-Henri.Jondot@wanadoo.fr>
> Page perso : http://perso.wanadoo.fr/phj
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev

Re: [gentoo-dev] Problem With TeX and opencm

[Matthew Kennedy]

It is actually a bug in the opencm ebuild and should goto
bugs.gentoo.org. The correct solution is to add:

        addwrite "/var/lib/texmf"
        addwrite "/usr/share/texmf"
        addwrite "/var/cache/fonts"

To the ebuild before the compilation takes place.

On Tue, 2002-07-09 at 19:31, Mark Cox wrote:
> That worked like a charm.
> 
> All you have to do is put
> export USE_VARTEXFONTS=1
> export VARTEXFONTS=${WORKDIR}/fonts
> 
> and bingo it works.
> I wonder who we should talk to to put this somewhere for other people who might
> encounter the same problem.

-- 
Matthew Kennedy
Gentoo Linux Developer

Re: [gentoo-dev] Problem With TeX and opencm

[Pierre-Henri Jondot]

> It is actually a bug in the opencm ebuild and should goto
> bugs.gentoo.org. The correct solution is to add:
> 
>         addwrite "/var/lib/texmf"
>         addwrite "/usr/share/texmf"
>         addwrite "/var/cache/fonts"
> 
> To the ebuild before the compilation takes place.
> 
> -- 
> Matthew Kennedy
> Gentoo Linux Developer
> 
No it is not a bug because the opencm ebuild hasn't been commited yet !
(or hadn't...)

(Neither has the pari-gp ebuild I'm doing right now)

It was a question of the writer of this, to be committed, ebuild to know the
proper way to allow opencm to build its documentation without making sandbox
complain about violations...

Had I read your answer a day ago, I would not have spent some (not so
precious !) unnecessary time in tetex documentation to force the generation
of fonts under /var/tmp.

I do agree that it is better to generate the fonts (pks and metrics) once
and for all, as it won't have to be done again for viewing the dvi so I'll
use the addwrite commands you suggest to the pari ebuild I'm doing right
now.

>From what I read in the tetex documentation, I guess that only the line
about /usr/share/texmf is needed, but in case I will insert the three of
them.

-- 
Pierre-Henri Jondot <Pierre-Henri.Jondot@wanadoo.fr>
Page perso : http://perso.wanadoo.fr/phj

Re: [gentoo-dev] Problem With TeX and opencm

[Chad M. Huneycutt]

Matthew Kennedy wrote:
> It is actually a bug in the opencm ebuild and should goto
> bugs.gentoo.org. The correct solution is to add:
> 
>         addwrite "/var/lib/texmf"
>         addwrite "/usr/share/texmf"
>         addwrite "/var/cache/fonts"

Is this in some way superior to the environment variable solution 
suggested?  It seems like the best solution will always be to, when 
possible, write to the sandbox, and that is what that solution allows. 
However, I am not familiar with exactly what is going on, so maybe 
merging those files doesn't work correctly, or some paths would be 
incorrect?

Chad

Re: [gentoo-dev] Problem With TeX and opencm

[Matthew Kennedy]

On Wed, 2002-07-10 at 08:01, Chad M. Huneycutt wrote: 
> >         addwrite "/var/lib/texmf"
> >         addwrite "/usr/share/texmf"
> >         addwrite "/var/cache/fonts"
> 
> Is this in some way superior to the environment variable solution 
> suggested?  It seems like the best solution will always be to, when 

Yes, in that you don't have to tell the user to configure tetex before
you emerge opencm to make use of those env vars.

-- 
Matthew Kennedy
Gentoo Linux Developer

Re: [gentoo-dev] Problem With TeX and opencm

[Chad Huneycutt]

Matthew Kennedy wrote:
> On Wed, 2002-07-10 at 08:01, Chad M. Huneycutt wrote: 
> 
>>>        addwrite "/var/lib/texmf"
>>>        addwrite "/usr/share/texmf"
>>>        addwrite "/var/cache/fonts"
>>
>>Is this in some way superior to the environment variable solution 
>>suggested?  It seems like the best solution will always be to, when 
> 
> 
> Yes, in that you don't have to tell the user to configure tetex before
> you emerge opencm to make use of those env vars.
> 

Huh?  They can't be set in the ebuild?

-- 
Chad Huneycutt
Ph.D. Student
Georgia Tech College of Computing
http://www.cc.gatech.edu/~chadh