Minor terminfo problem (was Re: Garbage man pages)

[Christopher Faylor]

On Thu, Jun 18, 2009 at 11:46:50AM +0200, Corinna Vinschen wrote:
>On Jun 18 10:36, Haojun Bao wrote:
>> 
>> Dave Korn <dave.korn.cygwin@googlemail.com> writes:
>> >
>> >   I said I'd check: there doesn't seem anything wrong with the packaging,
>> > which hasn't changed in a couple of years now; the most likely thing is that
>> > you and Bao experienced some kind of failure during running the postinstall
>> > scripts.  Checking the log files /var/log/setup.* might show some indication
>> > of the problem.  (But it also might not, error-handling paths are a known
>> > weakness in setup.exe.)
>> 
>> Thanks:-)
>> 
>> I can confirm your guess, the following lines are in my /var/log/setup.log:
>> 
>>     2009/06/04 18:06:49 running: C:\cygwin\bin\bash.exe --norc --noprofile -c /etc/postinstall/man.sh
>>     2009/06/04 18:06:50 abnormal exit: exit code=127
>>     
>> Here's a complete list of abnormal exits, note that I did 2 install,
>> first time is default, second time is full-install. I used 
>> `grep abnormal -B 1 setup.log':
>> 
>>     2009/06/04 18:06:44 running: C:\cygwin\bin\bash.exe --norc --noprofile -c /etc/postinstall/000-cygwin-post-install.sh
>>     2009/06/04 18:06:47 abnormal exit: exit code=127
>
>Works fine for me.  I just made a new 1.7 installation from scratch two
>days ago, and all the bash calls work as expected, except for a minor
>problem in the terminfo postinstall:
>
>2009/06/16 11:13:37 running: C:\cygwin-1.7\bin\bash.exe --norc --noprofile -c /etc/postinstall/terminfo0.sh
>chmod: cannot operate on dangling symlink `Eterm-color'
>
>2009/06/16 11:13:45 running: C:\cygwin-1.7\bin\bash.exe --norc --noprofile -c /etc/postinstall/terminfo.sh
>chmod: cannot operate on dangling symlink `Eterm-color'
>
>ETerm-color points to ../E/ETerm, but the directory is called 'e',
>not 'E'.  That's a problem when using case-sensitivity like on a couple
>of my test machines.
>
>Chuck?  Can you fix this in a manner which also works on case-sensitive
>filesyatems, please?

Maybe we should fix this in setup.exe too by setting the terminal type
to "dumb".  In fact, maybe we should cleanse the environment in setup.exe
before running any program, if we aren't doing that already.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/