[from private email]
of course it was WinME (as guessed).
--
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/
--- Begin Message ---
Reini Urban wrote:
Hi Alex,
Alexander Colesnicov schrieb:
I tried to install cygwin and it hanged when executing
/etc/postinstall/post-texmf.sh . To proceed further
Hi Alex,
Alexander Colesnicov schrieb:
I tried to install cygwin and it hanged when executing
/etc/postinstall/post-texmf.sh . To proceed further, I marked this
script as "done" and all the rest was OK. Then I started cygwin and run
this script manually. I found that it was a conflict with my exist
Corinna Vinschen writes:
Corinna,
> since the tetex settings are so dependent of environment variables
> and since the environment variables are shared with different tetex
> implementations, wouldn't it be better to split the tetex installation
> into two files?
>
> First, the postinstall script
Jan,
On Sep 13 21:23, Jan Nieuwenhuizen wrote:
> Because I do not like to make the wrong fix. In this case, it will
> probably hurt very few people, so it would make sense to think a bit
> and do it correctly, if possible.
>
> See, I can easily add unsetting bunch of variables to post-texmf.mf,
Igor Pechtchanski writes:
>> FWIW, the way teTeX works, most variables set in texmf.cnf are
>> overridden by the environment; it would be next to impossible to
>> guarantee a successful teTeX environment after logging in if variables
>> from the WINDOWS are allowed to silently enter the Cygwin
>>
On Mon, 13 Sep 2004, Jan Nieuwenhuizen wrote:
> Igor Pechtchanski writes:
>
> > Not really. As Max said, the environment in which the postinstall scripts
> > run is the same as the one you'd get when you run them on the command line
> > (albeit from a non-login /bin/sh). That environment will co
Christopher Faylor writes:
> No, you can't have a completely empty environment on Windows. There
> are some environment variables that really have to be there.
I understand that, can't we make a list of those essential variables,
and wouldn't it be nice if setup.exe copied those essential variab
On Mon, Sep 13, 2004 at 08:54:11PM +0200, Jan Nieuwenhuizen wrote:
>Igor Pechtchanski writes:
>
>> Not really. As Max said, the environment in which the postinstall scripts
>> run is the same as the one you'd get when you run them on the command line
>> (albeit from a non-login /bin/sh). That env
Igor Pechtchanski writes:
> Not really. As Max said, the environment in which the postinstall scripts
> run is the same as the one you'd get when you run them on the command line
> (albeit from a non-login /bin/sh). That environment will contain all of
> the Windows-set environment variables. I
On Mon, 13 Sep 2004, Jan Nieuwenhuizen wrote:
> Igor Pechtchanski writes:
>
> > FWIW, it was the original poster who wrote the below -- all of my comments
> > got snipped out.
>
> Sorry.
No problem, just pointing out the correct attribution. :-)
> > If an empty environment is needed, why not use
Igor Pechtchanski writes:
> FWIW, it was the original poster who wrote the below -- all of my comments
> got snipped out.
Sorry.
> If an empty environment is needed, why not use "env -i" in the postinstall
> script?
Because that's a bit like fixing the bug inside-out?
Jan.
--
Jan Nieuwenhuiz
On Mon, 13 Sep 2004, Jan Nieuwenhuizen wrote:
> Igor Pechtchanski writes:
FWIW, it was the original poster who wrote the below -- all of my comments
got snipped out.
> >> I found that it was a conflict with my existing fpTeX installation
> >> (fpTeX is a TeTeX port to Windows) that defined an en
Jan Nieuwenhuizen wrote:
Igor Pechtchanski writes:
I found that it was a conflict with my existing fpTeX installation
(fpTeX is a TeTeX port to Windows) that defined an environment
variable TEXMFCNF to one of Windows directories.
I feel that setup.exe should not use an unclean environment.
I'm not
Igor Pechtchanski writes:
>> I found that it was a conflict with my existing fpTeX installation
>> (fpTeX is a TeTeX port to Windows) that defined an environment
>> variable TEXMFCNF to one of Windows directories.
I feel that setup.exe should not use an unclean environment.
>> The script post-te
On Fri, 10 Sep 2004, Alexander Colesnicov wrote:
> Dear Sir/Madam,
>
> I tried to install cygwin and it hanged when executing
> /etc/postinstall/post-texmf.sh . To proceed further, I marked this
> script as "done" and all the rest was OK. Then I started cygwin and run
> this script manually. I fou
Dear Sir/Madam,
I tried to install cygwin and it hanged when executing
/etc/postinstall/post-texmf.sh . To proceed further, I marked this
script as "done" and all the rest was OK. Then I started cygwin and run
this script manually. I found that it was a conflict with my existing
fpTeX installation
16 matches
Mail list logo