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: List-Archive: List-Post: List-Help: , Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com Subject: Re: /setup.html please read - feedback desired From: Robert Collins To: cygwin-apps AT cygwin DOT com In-Reply-To: <20011102212245.E31918@redhat.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> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.15 (Preview Release) Date: 03 Nov 2001 13:49:29 +1100 Message-Id: <1004755770.519.74.camel@lifelesswks> Mime-Version: 1.0 X-OriginalArrivalTime: 03 Nov 2001 02:53:48.0041 (UTC) FILETIME=[C29E0790:01C16412] On Sat, 2001-11-03 at 13:22, Christopher Faylor wrote: > On Sat, Nov 03, 2001 at 12:57:23PM +1100, Robert Collins wrote: > > Are we disagreeing about something? I am not sure anymore. :] > 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". > As I've said repeatedly, I expect that setup.hint will eventually hold > all of the information and setup.ini will be generated solely from this. > After that happens, eventually, I expect that there will be a file in > the package itself which contains this info and maybe setup.hint will > disappear. Correct. > 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. > to add 'prev' and 'curr' options unless version numbering is strange or > there is a 'test' requirement. Agreed. Rob