Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-apps-owner AT cygwin DOT com
List-Subscribe: <mailto:cygwin-apps-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-apps/>
List-Post: <mailto:cygwin-apps AT cygwin DOT com>
List-Help: <mailto:cygwin-apps-help AT cygwin DOT com>, <http://sources.redhat.com/lists.html#faqs>
Delivered-To: mailing list cygwin-apps AT cygwin DOT com
Message-ID: <3C126412.1060903@ece.gatech.edu>
Date: Sat, 08 Dec 2001 14:03:46 -0500
From: Charles Wilson <cwilson AT ece DOT gatech DOT edu>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.4) Gecko/20010914
X-Accept-Language: en-us
MIME-Version: 1.0
To: Jan Nieuwenhuizen <janneke AT gnu DOT org>
CC: cygwin-apps AT cygwin DOT com
Subject: Re: broken setup.hint files
References: <m3667hsrm9 DOT fsf AT appel DOT lilypond DOT org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-milter (http://amavis.org/)

Jan Nieuwenhuizen wrote:

> Hi,
> 
> After I added setup.hint support to my gen-ini script, I found that
> quite some setup.hint files are broken.  Most of them could be fixed
> by doing:
> 
>      hint="$(echo | cat $i/setup.hint - | grep -Ev '^(prev)|(curr|@) ' | sed -e 's/^\(\(category\)\|\(ldesc\)\|\(requires\)\|\(sdesc\)\|\(test\)\). */\1: /' | grep -v '^$')"


Ummm...they are not broken.  You just dislike some stylistic choices...

colons are optional, setup.hint doesn't NEED to have them.

Also, blindly removing the prev/curr/test markers is not a good thing 
either.  Sometimes (when upset's automatic version parser fails) you 
MUST sepecify curr/prev in the hint.  I don't know if any of the hint 
files you list below include the curr/prev markers for that reason, or if:

the hints may just be old.  Originally, the spec for hint files said 
"include curr and prev fields".  Later, it was changed to "that often 
causes confusion when folks forget to update the setup.hint.  Don't 
include curr/prev fields unless you must"

In my case, I will update a given setup.hint to follow that new 
*recommendation* (not requirement) the next time I update the package 
controlled by it, and not until then.  If it ain't broken (and it ain't) 
then don't fix it.

> 
> I found these
> 
>     ncurses
>     jpeg
>     libncurses5
>     libncurses6
>     libpng
>     tiff
>     tetex
>     textutils


--Chuck