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:51 +0200
Message-ID: <NGBBLLIAMFLGJEOAJCCEOEGFDEAA.garbage_collector@telia.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
Importance: Normal
In-Reply-To: <1064192432.24990.27.camel@localhost>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165

> From: Robert Collins

>
> In general, setup needs to be taught about classes of files:
> configuration files vs image files vs data and script files.
>
> Once that general concept is in place, we can:
> * support rpm and dpkg formats more effectively
> * add classes for things like apache
> * be smarter about rebasing
>
> etc etc etc

 I'm sure this is the way to go... I'm not that intimate with the details of
how setup works.
 My idea was based on a wish to "clean up" - for the moment.
I didn't expect it to become a "long time solution" :-)

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