Norbert Preining wrote:
> On So, 09 Jan 2011, Norbert Preining wrote:
>> > I think you can make yout patch cleaner
>> > by replacing /var/lib/texmf with $TEXMFSYSVARDIR,
>> > as this avoids new instances of hard-coded paths:
>>
>> And where is $TEXMFSYVARDIR defined?
>
> Umpf, yes, it is, sorry.
Norbert Preining wrote:
> On Mo, 03 Jan 2011, Hilmar Preusse wrote:
>> would be possible. We have a config file where things can be changed
>> and it may happen that people expect this can be done.
Well, it may - but it is written in (the TeX) policy that they should not.
>> And yes: I don't s
On So, 09 Jan 2011, Norbert Preining wrote:
> > I think you can make yout patch cleaner
> > by replacing /var/lib/texmf with $TEXMFSYSVARDIR,
> > as this avoids new instances of hard-coded paths:
>
> And where is $TEXMFSYVARDIR defined?
Umpf, yes, it is, sorry. Complicated the origin of all this
On Di, 04 Jan 2011, Braun Gábor wrote:
> I withdraw my proposal.
> I don't think being able to move trees is worth opening up the worms.
Yes.
> I think you can make yout patch cleaner
> by replacing /var/lib/texmf with $TEXMFSYSVARDIR,
> as this avoids new instances of hard-coded paths:
And wher
On Mo, 03 Jan 2011, Hilmar Preusse wrote:
> would be possible. We have a config file where things can be changed
> and it may happen that people expect this can be done.
>
> And yes: I don't see either a good reason to do so.
Then we should simply add a BIG FAT WARNING to the various texmf.d/ fi
> To make it completely clear: Debian TeX Live does not support
> moving of arbitrary trees by changing variables in texmf.cnf.
>
> If we allow that this will be a huge set of worms we open up.
I withdraw my proposal.
I don't think being able to move trees is worth opening up the worms.
I think y
On Mon, Jan 03, 2011 at 09:41:04AM +0100, Hilmar Preusse wrote:
> Happy new year,
>
> > > Not good[TM]. I'll open a wishlist bug to have that changed. Should
> > > be that hard to source /etc/texmf/texmf.cnf at the beginning of these
> >
> > Can you transplant the X hierarchy somewhere else? I su
On 02.01.11 Norbert Preining (prein...@logic.at) wrote:
> On Fr, 31 Dez 2010, Hilmar Preusse wrote:
Happy new year,
> > Not good[TM]. I'll open a wishlist bug to have that changed. Should
> > be that hard to source /etc/texmf/texmf.cnf at the beginning of these
>
> Can you transplant the X hiera
On Fr, 31 Dez 2010, Hilmar Preusse wrote:
> > To make it completely clear: Debian TeX Live does not support
> > moving of arbitrary trees by changing variables in texmf.cnf.
> >
> Not good[TM]. I'll open a wishlist bug to have that changed. Should
> be that hard to source /etc/texmf/texmf.cnf at t
On 30.12.10 Norbert Preining (prein...@logic.at) wrote:
Hi,
> Most of our scripts (the ones written for Debian) expect TEXMFDIST to
> be /u/s/texmf-texlive and TEXMFSYSVAR to be /v/l/texmf.
>
> Looking through the whole trigger code I see many instances of that.
>
> To make it completely clear
On Di, 28 Dez 2010, Hilmar Preusse wrote:
> > AFAIK the paths texlive uses can be freely configured by the sysadmin.
> > So I think the paths /var/lib/texmf/ etc in the examples are
> > simplification to clearly state the idea and not meant to appear
> > in real code.
> >
> > Therefore I suggest t
Hilmar Preusse wrote:
>> Therefore I suggest to modify the proposed patch of ponstinst.in to
>> obtain the path from the relevant configuration variable
>> (which I guess is TEXMFSYSVAR as this seems to be the one used by
>> updmap-sys).
kpsewhich --expand-var='$TEXMFSYSVAR'
> Could you care
On 27.12.10 Braun Gábor (bra...@renyi.hu) wrote:
Hi Norbert,
> Package: tex-common
> Followup-For: Bug #607857
>
> AFAIK the paths texlive uses can be freely configured by the sysadmin.
> So I think the paths /var/lib/texmf/ etc in the examples are
> simplification to clearly state the idea and
Package: tex-common
Followup-For: Bug #607857
AFAIK the paths texlive uses can be freely configured by the sysadmin.
So I think the paths /var/lib/texmf/ etc in the examples are
simplification to clearly state the idea and not meant to appear
in real code.
Therefore I suggest to modify the propos
14 matches
Mail list logo
