Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Date: Fri, 29 Oct 2004 16:42:44 -0400 (EDT)
From: Igor Pechtchanski <pechtcha@cs.nyu.edu>
Reply-To: cygwin@cygwin.com
To: Alex Vinokur <alexvn@connect.to>
cc: cygwin@cygwin.com
Subject: Re: startup problem // no longer works // profile not called
In-Reply-To: <clu290$ecr$1@sea.gmane.org>
Message-ID: <Pine.GSO.4.61.0410291638120.14835@slinky.cs.nyu.edu>
References: <1098655354.9421.ezmlm@cygwin.com> <200410250937.34058.d_baron@012.net.il> <clidg8$s21$1@sea.gmane.org> <417CBF56.E5BD31C0@dessent.net> <clikgs$eq6$1@sea.gmane.org> <Pine.GSO.4.61.0410250916210.28948@slinky.cs.nyu.edu> <clj0b6$lab$1@sea.gmane.org> <Pine.GSO.4.61.0410251147450.16595@slinky.cs.nyu.edu> <clj961$je1$1@sea.gmane.org> <Pine.GSO.4.61.0410251307490.16595@slinky.cs.nyu.edu> <clknka$4rq$1@sea.gmane.org> <Pine.GSO.4.61.0410261333000.20919@slinky.cs.nyu.edu> <clqn4f$ck2$1@sea.gmane.org> <Pine.GSO.4.61.0410281021110.8902@slinky.cs.nyu.edu> <clu290$ecr$1@sea.gmane.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Scanned-By: MIMEDefang 2.39

On Fri, 29 Oct 2004, Alex Vinokur wrote:

> "Igor Pechtchanski" wrote:
> > On Thu, 28 Oct 2004, Alex Vinokur wrote:
> [snip]
> > > It seems that I got rid of problem "bash: kpsexpand: command not found".
> >
> > Great.  So it was simply a missing dependency problem.
>
> I don't understand how the problem has been resolved.

Some script inserted by lilypond into the login script path (presumably
/etc/profile.d/lilypond-profile.sh) contained an invocation of kpsexpand.
Since kpsexpand is part of the tetex-bin package, installing tetex-bin got
rid of the "not found" message.

> > > However,
> > > $ find /etc/postinstall -name \*.done | sed 's/\.done$//' | xargs cygcheck -f | uniq > postinstall.txt  // Attached
> > > postinstall.txt  contains a lot of files. Is it correct?
> >
> > Sure it is.  The above command simply lists all the packages installed on
> > your machine that have postinstall scripts -- nothing wrong with having
> > them.  The reason I asked you to get this information initially was that
> > because of your screwed up mounts the postinstall scripts may not have run
> > properly, and reinstalling the packages was one way of getting them to
> > re-run, so this showed which packages to reinstall.
> [snip]
>
> What do the postinstall scripts do?

They do post-installation fix-up of package files (generate configuration,
conditionally add symlinks, do installation-specific stuff).

> Who (and when) invokes them?

setup.exe, after installing all the packages.

There are also preremove scripts that are run before the corresponding
packages are removed.
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha@cs.nyu.edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor@watson.ibm.com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski, Ph.D.
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"The Sun will pass between the Earth and the Moon tonight for a total
Lunar eclipse..." -- WCBS Radio Newsbrief, Oct 27 2004, 12:01 pm EDT

--
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/

