On Mon, 10 Jul 2006, Frank Küster wrote:
Oliver-Mark Cordes <[EMAIL PROTECTED]> wrote:
On Mon, 10 Jul 2006, Frank Küster wrote:
[...]
Strange that it says "(/usr/bin/amstex", on my system it's "(./amstex".
But anyway.
Does tex translate any filename into realnames?
Pardon? What do you mean with this question?
From my experience in many TeX documents I found something like
\include amstex which includes the first file of amstex.* (or priviledged
filename extensions). In the *tex output you always see which real file is
included,right?
Hm, I don't think this makes sense, or is even doable. It's a feature
that TeX reads files in the current directory - a feature that can also
be used for generating customized formats.
On the other hand it (the feature) probably doesn't make any sense in
the post-installation script. We could fix this by changing directory
to / or /tmp. But we cannot be sure that there isn't a file "amstex" in
any of these directories.
I think it isn't unreasonable to expect that someone wants to create a
file "amstex" in /tmp, for whatever reason. But I can't think of a
reason to change directory to /usr/bin. Why did you do it?
I was packaging own debian-Packages (some python modules and own
programs) and checked the installations scripts. This doesn't belong
to any normal upgrades ;-)
I still don't see a reason to change the current directory to
/usr/bin/.
Okay, from the beginning: When I did my upgrade my current directory was
/usr/bin and the installation/configuration with dpkg failed. apt-get -f
install started from the same directory worked. The reason why I filed a
bug report is that from my understanding of the debian policy all packages
should be installed from whatever directory possible, right?
/usr/bin has nothing to do with the tex-installation for whatever reason
my cwd was /usr/bin until I recognized that configuring tetex-base failed
because some scripts included teh binary amstex.
From my experience as a programmer/administrator I know that some programs
behave differently in different directories. So as a consequence I thought
that it would be nice to change the configuration slightly to avoid
further problems, because you should expect always the worst case ;-)
I know about this "feature" and sometimes
I'm not happy about this, but it is a feature not a bug ;-) But anyway
to switch to a "neutral" directory would help.
Well, as I said it would cause other breakage (you can't have a file
"amstex" in /tmp/ any more, or wherever).
PS: I don't send this mail to the BTS because there is no new
information regarding the BUG I posted.
No new information about your system; but the question is still open
whether we need to change anything or not. Obviously you think that the
bug shouldn't just be closed (which I would personally prefer), so the
discussion what to do instead and why is relevant for that bug, and
should be archived?
Regards, Frank
Yes, I think the configuration should take care of the directory from
which the configuration is started until this BUG can be closed. The idea
from Florent to use a temporary directory in /tmp is easy to implement and
should work. I don't have the time to test it but it really sounds like a
good idea.
Oliver
--
(O> (0- _o) -O)
//\ //\ /\\ /\\
V_/_ V_/_ _\_V _\_V
Dr. Oliver-M. Cordes E-Mail: [EMAIL PROTECTED]
WWW-URL: http://www.astro.uni-bonn.de/~ocordes/
Argelander Institut fuer Astronomie
Universitaet Bonn Phone: (49) 228 / 73-5656
Auf dem Huegel 71 Fax: (49) 228 / 73-3672
D - 53121 Bonn Germany
Private address: Witterschlickerstr. 22 , D - 53123 Bonn
Private phone: (49) 228 / 7482582
