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 Date: Tue, 2 Oct 2001 17:36:34 -0400 From: Christopher Faylor To: cygwin-apps AT cygwin DOT com Subject: Re: setup.ini, setup.hint, and update-setup Message-ID: <20011002173634.A4473@redhat.com> Reply-To: cygwin-apps AT cygwin DOT com Mail-Followup-To: cygwin-apps AT cygwin DOT com References: <3BBA2FAA DOT 7060805 AT ece DOT gatech DOT edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3BBA2FAA.7060805@ece.gatech.edu> User-Agent: Mutt/1.3.21i On Tue, Oct 02, 2001 at 05:20:42PM -0400, Charles Wilson wrote: >While setup.exe can handle multi-line "ldesc" entries in setup.ini, the >update-setup script used to generate that file from the setup.hint's >will not create the correct results if the hint file has a multi-line >ldesc entry. > >Question: > >There are two ways to address this, that I can see: > 1) fix update-setup to deal with multi-line entries > 2) require that all entries fit on a single line -- but it can be >very long... > >I'm all for #2. Comments? I have a corollary question. Can setup.exe deal with multi-line ldesc's? If not then we need to do some variation of 2. >Oh, and one other thing: update-setup doesn't parse the "category" or >"requires" entry from the hint file. Right. I mentioned this a while ago and Robert submitted a patch for this but, frankly, I am not really looking for update-setup patches. I'm not going to guarantee that update-setup is around for the long haul. That's one reason why it is not publicly available. cgf