This is the mail archive of the
mailing list for the Cygwin project.
Re: SUGGESTION wrt preremove / postinstall / preinstall (RE: [FAQ] Packages reported as "Incomplete" by "cygcheck -c")
- From: Igor Pechtchanski <pechtcha at cs dot nyu dot edu>
- To: "Hannu E K Nevalainen (garbage mail)" <garbage_collector at telia dot com>
- Cc: cygwin at cygwin dot com
- Date: Sun, 21 Sep 2003 19:10:13 -0400 (EDT)
- Subject: Re: SUGGESTION wrt preremove / postinstall / preinstall (RE: [FAQ] Packages reported as "Incomplete" by "cygcheck -c")
- References: <NGBBLLIAMFLGJEOAJCCEIEGCDEAA.firstname.lastname@example.org>
- Reply-to: cygwin at cygwin dot com
On Mon, 22 Sep 2003, Hannu E K Nevalainen (garbage mail) wrote:
> > From: Igor Pechtchanski
> > Sent: Monday, September 15, 2003 7:18 PM
> > Q: Why are "apache" and "mod_*" packages reported as "Incomplete"?
> > A: The "apache" and "mod_*" packages use a postinstall script that renames
> > an originally installed directory. Therefore, that directory is not
> > found by "cygcheck -c". Suggestions on how to deal with this are
> > welcome (patches doubly so ;-)).
> post/preinstall scripts that MOVE or RENAME files must "retain the
> $ mv prev-name new-name
> $ ln -s prev-name new-name
> preremove script:
> $ rm prev-name
> $ rm new-name
> Would this work?
> Could at least be a "interrim solution", don't you think?
> Is it possible to list (add) a filename in the archive in some way? (HOW?)
> /Hannu E K Nevalainen
Most postinstall scripts accomplish exactly that by copying the files
instead of moving them. I don't see that this is too practical in the
case of apache, as this is a whole deeply nested directory -- I'm guessing
the "mv" is an optimization.
The "right" solution, IMO, would be to somehow mark the affected files as
"movable by postinstall scripts", so that cygcheck doesn't attempt to
locate them. One way to do this is to designate a directory in the Cygwin
FHS for "scratch files", and have cygcheck not check any files or
directories installed into that tree.
Some solutions specifically for apache (considering that it provides a
default www tree) might be to distribute the tree separately, in a helper
package (kind of like tetex-* do with the texmf tree), or to package the
tree as a .tar file and untar it in the postinstall script (and keep the
tar file around). The mod_* postinstall scripts should simply keep the
original (unrebased) DLLs around.
P.S. I'm not sure I understand the last question.
|\ _,,,---,,_ email@example.com
ZZZzz /,`.-'`' -. ;-;;,_ firstname.lastname@example.org
|,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D.
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster." -- Patrick Naughton
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html