delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2002/09/25/21:42:36

Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-Id: <5.1.0.14.2.20020925182421.03056948@pop3.cris.com>
X-Sender: rrschulz AT pop3 DOT cris DOT com
Date: Wed, 25 Sep 2002 18:42:38 -0700
To: cygwin AT cygwin DOT com
From: Randall R Schulz <rrschulz AT cris DOT com>
Subject: Re: Lost /bin/latex?
In-Reply-To: <Pine.GSO.4.44.0209252000170.12726-100000@slinky.cs.nyu.edu
>
References: <5 DOT 1 DOT 0 DOT 14 DOT 2 DOT 20020925162445 DOT 02c96ea8 AT pop3 DOT cris DOT com>
Mime-Version: 1.0

Igor,


At 17:07 2002-09-25, you wrote:
>This is probably due to the fact that usr/bin/readlink.exe and
>usr/man/man1/readlink.1 were included (erroneously, I guess) in the
>tetex-bin-20020530-3 distribution, instead of listing a dependency on
>cygutils.  The new distrib corrects that problem, but uninstalling the old
>one resulted in losing readlink.  As this is not something that can be
>fixed in the tetex package, people will probably just have to reinstall
>cygutils.

All well and good (and now that you mention it, I think I remember reading 
about this glitch a while back), but doesn't that create a bit of a 
catch-22 for the tetex post-install script when it attempts to invoke 
readlink? How is it possible to get that to run correctly? Must I reinstall 
cygutils (obviously yes) and then also reinstall tetex?

Well, I tried that, and to the best of my ability to scan the stuff 
whizzing by in the post-install script's window, the diagnostic about a 
missing readlink did not appear. It seems that the overall impression of 
the post-install activity as it flashed before my eyes was rather different 
than what I remember from upgrading tetex earlier today. I wonder how 
critical that readlink is to the overall activity and success of the tetex 
post-install script(s)?

All's well that ends... I guess.

Randall Schulz
Mountain View, CA USA


>For the future, it would probably be a good idea to have the output of the
>postinstall scripts logged somewhere (setup.log.full?).  Is setup.exe
>responsible for running the scripts?
>
>Also, for the package builder, it might be nice to get a warning if there
>are file clashes in some packages.  This is probably more of a
>challenge...
>         Igor
>
>On Wed, 25 Sep 2002, Randall R Schulz wrote:
>
> > Hi,
> > I upgraded my tetex just now (20020911) and the diagnostic that caught my
> > attention was that the "readlink" command could not be found.
> >
> > If the post-install command output is logged, I cannot find it. Is it kept
> > somewhere? The only lines in the files "setup.log" and "setup.log.full" in
> > "/var/log" that mention "readlink" are these ominous ones from 
> setup.log.full:
> >
> > unlink D:/cygwin/bin//readlink.exe
> > unlink D:/cygwin/usr/man/man1/readlink.1


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019