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
From: "Hannu E K Nevalainen \(garbage mail\)" <garbage_collector AT telia DOT com>
To: <cygwin AT cygwin DOT com>
Subject: RE: SUGGESTION wrt preremove / postinstall / preinstall (RE: [FAQ]  Packages reported as "Incomplete" by "cygcheck -c")
Date: Mon, 22 Sep 2003 10:55:50 +0200
Message-ID: <NGBBLLIAMFLGJEOAJCCEMEGFDEAA.garbage_collector@telia.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
Importance: Normal
In-Reply-To: <Pine.GSO.4.56.0309211859230.12411@slinky.cs.nyu.edu>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165

> From: Igor Pechtchanski

> On Mon, 22 Sep 2003, Hannu E K Nevalainen (garbage mail) wrote:
>
> > > From: Igor Pechtchanski
> > > Sent: Monday, September 15, 2003 7:18 PM
> >
> > <SNIP>
> > > 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 ;-)).
> >
> > Suggestion:
> >   post/preinstall scripts that MOVE or RENAME files must "retain the
> > filename"
> > i.e.
> >
> >         $ 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.

 Ok. Then my suggestion is just replicating current status. Well... ;-)

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

 This doesn't appeal to my "estetic sense"... ;-7

> 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.
> 	Igor

That would allow a "reset" of those. A positive thing? Never mind.

> P.S. I'm not sure I understand the last question.

 Ahh... beeing tired again -> too few words.

The idea was to add the "name of the copy" to the "list of files in this
package", and to do this during pre/postinstall - if that is feasible.

 Now that I read it once again, the idea doesn't seems so good anymore.

/Hannu E K Nevalainen, B.Sc. EE - 59?16.37'N, 17?12.60'E
-- UTC+01, DST -> UTC+02  --
--END OF MESSAGE--


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