Mailing-List: contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-apps-owner AT sourceware DOT cygnus DOT com
List-Subscribe: <mailto:cygwin-apps-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-apps/>
List-Post: <mailto:cygwin-apps AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-apps-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/lists.html#faqs>
Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com
Date: Fri, 2 Nov 2001 21:55:04 -0500
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin-apps AT cygwin DOT com
Subject: Re: /setup.html please read - feedback desired
Message-ID: <20011102215504.M31918@redhat.com>
Reply-To: cygwin-apps AT cygwin DOT com
Mail-Followup-To: cygwin-apps AT cygwin DOT com
References: <1004700277 DOT 7488 DOT 2 DOT camel AT lifelesswks> <3BE2E3D3 DOT 1050201 AT ece DOT gatech DOT edu> <20011102134846 DOT H26975 AT redhat DOT com> <1004745374 DOT 9086 DOT 77 DOT camel AT lifelesswks> <20011102195741 DOT A31898 AT redhat DOT com> <1004750730 DOT 519 DOT 26 DOT camel AT lifelesswks> <20011102204613 DOT B31918 AT redhat DOT com> <1004752644 DOT 521 DOT 47 DOT camel AT lifelesswks> <20011102212245 DOT E31918 AT redhat DOT com> <1004755770 DOT 519 DOT 74 DOT camel AT lifelesswks>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1004755770.519.74.camel@lifelesswks>
User-Agent: Mutt/1.3.21i

On Sat, Nov 03, 2001 at 01:49:29PM +1100, Robert Collins wrote:
>On Sat, 2001-11-03 at 13:22, Christopher Faylor wrote:
>> On Sat, Nov 03, 2001 at 12:57:23PM +1100, Robert Collins wrote:
>> I was just reacting to Chuck's assertion that setup.hint is now the
>> "normal" method not the "fallback" method for version handling.  I don't
>> agree with that.
>
>I happen to agree with Chuck. All the metadata to drive the new setup
>*can* be placed directly into setup.ini or setup.hint. I'm in favour of
>simply saying "put it in setup.hint". 

Then, I guarantee that, until there is a simple tool to manipulate
setup.hint, we will see problems, because people will forget to update
prev/curr in setup.hint.

It has happened to me, it has happened to Corinna.  It has happened to
others.

>>Right now most of the information is concentrated in setup.ini.  It was
>>a lot easier for me to manipulate all of the package info in setup.ini
>>than it would have been to have it in 88 different directories.  I
>>expect this to change.
>
>I've no objection to *you* editing setup.ini.  I've an objection to new
>maintainers doing *anything* directly to setup.ini.  And the doco we
>are writing is for *new maintainers* - like Kevin.

Right:
* I hope that package maintainers will start updating the info in
* setup.ini by adding setup.hint files.

cgf