Bug#607857: tex-common: Hard-coded path in proposed patch
Norbert Preining prein...@logic.at 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 see either a good reason to do so. Then we should simply add a BIG FAT WARNING to the various texmf.d/ files that changing anything in the trees section is not supported. Actually this is a remaining thing from tetex times I happily would get rid off. Sounds worthwile... Regards, Frank -- Dr. Frank Küster VCD Miltenberg, ADFC Aschaffenburg-Miltenberg B90/Grüne KV Miltenberg Debian Developer (TeXLive) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#607857: tex-common: Hard-coded path in proposed patch
Norbert Preining prein...@logic.at 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. Complicated the origin of all this code ... common.variables ... I am sure this file made lots of sense bach when we had tex-common, tetex and texlive, all with separate update cycles. Now with only texlive having a separate upstream, we could maybe get rid of it, and simply manually change in tex-common what the new TeX Live upstream version requires. But I'm not sure. Regards, Frank -- Dr. Frank Küster VCD Miltenberg, ADFC Aschaffenburg-Miltenberg B90/Grüne KV Miltenberg Debian Developer (TeXLive) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#607857: tex-common: Hard-coded path in proposed patch
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 where is $TEXMFSYVARDIR defined?
No need to add another patch, I can work it out myself ;-)
Best wishes
Norbert
Norbert Preiningprein...@{jaist.ac.jp, logic.at, debian.org}
JAIST, Japan TeX Live Debian Developer
DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094
GLINSK (n.)
A hat which politicians but to go to Russia in.
--- Douglas Adams, The Meaning of Liff
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#607857: tex-common: Hard-coded path in proposed patch
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 code ...
common.variables ...
Anyway, changed and committed.
Best wishes
Norbert
Norbert Preiningprein...@{jaist.ac.jp, logic.at, debian.org}
JAIST, Japan TeX Live Debian Developer
DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094
LOWER PEOVER (n.)
Common solution to the problems of a humby (q.v.)
--- Douglas Adams, The Meaning of Liff
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#607857: tex-common: Hard-coded path in proposed patch
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 you can make yout patch cleaner by replacing /var/lib/texmf with $TEXMFSYSVARDIR, as this avoids new instances of hard-coded paths: Index: debian/postinst.in === --- debian/postinst.in (revision 4780) +++ debian/postinst.in (working copy) @@ -144,7 +144,7 @@ # call updmap with --nohash so that no ls-R files # are created in /usr/local/share/texmf/ # see bug report #607857 -# instead of that we call mktexlsr /var/lib/texmf +# instead of that we call mktexlsr $TEXMFSYSVARDIR # afterwards. This can be done without checks as # we know that dhit_libkpathsea_configured and # since mktexlsr and updmap are in the same package @@ -153,14 +153,14 @@ rm -f $tempfile echo done. tempfile=$(mktemp -p /tmp mktexlsr.) -printf Running mktexlsr /var/lib/texmf ... -if mktexlsr /var/lib/texmf $tempfile 21 ; then +printf Running mktexlsr $TEXMFSYSVARDIR ... +if mktexlsr $TEXMFSYSVARDIR $tempfile 21 ; then rm -f $tempfile echo done. else exec 2 echo -echo mktexlsr /var/lib/texmf failed. Output has been stored in +echo mktexlsr $TEXMFSYSVARDIR failed. Output has been stored in echo $tempfile echo Please include this file if you report a bug. echo Best wishes, Gábor Braun -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#607857: tex-common: Hard-coded path in proposed patch
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/ files
that changing anything in the trees section is not supported.
Actually this is a remaining thing from tetex times I happily
would get rid off.
There should be *ONE* texmf.cnf in /usr/sharee/texmf/web2c which defines
everything for Debian, and people can add overriding entries in
/etc/texmf/web2c/texmf.cnf, single lines for TEXMFLOCAL or so.
This is what we do in proper TeX Live, ther eis the one in
texlive/2010/texmf/web2c/texmf.cnf
which is managed by the package manger and updated now and then, and
people can use
texlive/2010/texmf.cnf
to make adjustments, like changing TEXMFLOCAL.
That is something I would like to see for Debian, too
Best wishes
Norbert
Norbert Preiningprein...@{jaist.ac.jp, logic.at, debian.org}
JAIST, Japan TeX Live Debian Developer
DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094
FRADDAM (n.)
The small awkward-shaped piece of cheese which remains after grating a
large regular-shaped piece of cheese and enables you to cut your
fingers.
--- Douglas Adams, The Meaning of Liff
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#607857: tex-common: Hard-coded path in proposed patch
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 hierarchy somewhere else? I suspect not. Can you move /usr/share/gnome-* somewhere else? I suspect not. I didn't check, but I suspect these packages don't even pretend this 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. H. -- sigmentation fault -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#607857: tex-common: Hard-coded path in proposed patch
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 suspect not.
Can you move /usr/share/gnome-* somewhere else? I suspect not.
I didn't check, but I suspect these packages don't even pretend this
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.
Happy new year to all, too!
Most significantly, the tex-common postinst is designed to handle the
installation of new files through the package maintenance system. The
files in those packages will be installed into the standard places on
the system, and tex-common behaves accordingly:
/usr/share/texmf{,-texlive} and /var/lib/texmf are the directories
handled by packages, and therefore tex-common should use those same
directories.
If a sysadmin wished to change this, they would have to divert every
single package installation - I can imagine this being painful and
pointless
Ho hum
Incidentally, the advice about using --nohash should be included in
the Debian TeX Policy so that other packages don't stumble upon this
bug.
Julian
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#607857: tex-common: Hard-coded path in proposed patch
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 the beginning of these
Can you transplant the X hierarchy somewhere else? I suspect not.
Can you move /usr/share/gnome-* somewhere else? I suspect not.
I am not sure if we actually want that. I don't see any advantage
in that. But please, go ahead.
The only place that *might* be useful to be shifted around is
TEXMFSYSVAR ... anything else I don't want to be allowed to moved.
Best wishes
Norbert
Norbert Preiningprein...@{jaist.ac.jp, logic.at, debian.org}
JAIST, Japan TeX Live Debian Developer
DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094
You're bound to be unhappy if you optimize everything.
--- Donald E. Knuth
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#607857: tex-common: Hard-coded path in proposed patch
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: 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 the beginning of these scripts and set the values of TEXMFMAIN, TEXMFDIST etc. only the variables are empty after /etc/texmf/texmf.cnf has been sourced. H. -- sigmentation fault -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#607857: tex-common: Hard-coded path in proposed patch
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 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).
I disagree. The path can in principle be changed in texmf.cnf, but this
is not what we support.
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: 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.
Best wishes
Norbert
Norbert Preiningprein...@{jaist.ac.jp, logic.at, debian.org}
JAIST, Japan TeX Live Debian Developer
DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094
HOFF (vb.)
To deny indignantly something which is palpably true.
--- Douglas Adams, The Meaning of Liff
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#607857: tex-common: Hard-coded path in proposed patch
Hilmar Preusse hill...@web.de 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 about this? I won't have time before my vacation. Regards, Frank -- Dr. Frank Küster VCD Miltenberg, ADFC Aschaffenburg-Miltenberg B90/Grüne KV Miltenberg Debian Developer (TeXLive) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#607857: tex-common: Hard-coded path in proposed patch
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 not meant to appear in real code. 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). Could you care about this? Thanks, Hilmar -- sigmentation fault -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#607857: tex-common: Hard-coded path in proposed patch
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 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). Best wishes, Gábor Braun -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
