X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-5.2 required=5.0	tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,RP_MATCHES_RCVD
X-Spam-Check-By: sourceware.org
X-IronPortListener: Outbound_SMTP
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqIAANXrZE6cKEdK/2dsb2JhbABDmFOPRXiBRgEBAQEDEig4FwIBCA0nAhAfEyUBAQQBGhqkMptThgpgBItyjGmLfA
From: "Buchbinder, Barry (NIH/NIAID) [E]" <BBuchbinder AT niaid DOT nih DOT gov>
To: "'Luke Kendall'" <luke DOT kendall AT cisra DOT canon DOT com DOT au>,
        "cygwin AT cygwin DOT com"	<cygwin AT cygwin DOT com>
Date: Mon, 5 Sep 2011 11:38:57 -0400
Subject: RE: More on Cygwin package naming
Message-ID: <0105D5C1E0353146B1B222348B0411A20A23D32202@NIHMLBX02.nih.gov>
References: <4E643ED8 DOT 3030100 AT cisra DOT canon DOT com DOT au>
In-Reply-To: <4E643ED8.3030100@cisra.canon.com.au>
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id p85FdMgm003738

Luke Kendall wrote on Sunday, September 04, 2011, at 11:16 PM
>In my previous mail I may have used the wrong term ("package"): the term 
>"package" seems to refer to each .tar.bz2 file (for the source and 
>install files of each version).  So perhaps I should instead be talking 
>about "@-names" - the name that appears after an "@" in setup.ini.
>
>Anyway, this is all related to me trying to determine the licenses for 
>each Cygwin "@-name".  What I've found so far is that:
>
>- Most cygwin @-names are simply the upstream "vendor"s project name.
>- But it's not rare for the name not to match at all.  This seems to 
>happen when a parent Freshmeat project is split into several cygwin 
>"@-named" pieces: in that situation, I can't find any automatable way to 
>tie the child names back to the parent.  E.g. libncurses9 is a cygwin 
>item from within the ncurses freshmeat project; or  libintl, 
>libintl{2,3,8} in cygwin, which are all part of the gettext project on 
>Freshmeat.  Currently I'm resorting to human inspection.
>
>I'd love to know if there's some way to determine this kind of 
>parent-child relationship.  Is there some setup.hint or upset or genini 
>file or info lurking around (where?) that I could scrape such 
>information out of?

The directory structure of the download release directory might help.
It is in the "install" line.  Using your gettext/libintl example:
install: release/gettext/libintl8/libintl8-0.18.1.1-1.tar.bz2 24375 bf501b540c768d63358426686c615530

Here's a start:

cat setup.ini | \
sed	-e '/^install: /!d'\
	-e '/\/_obsolete\//d' \
	-e 's,^install: release/,,' \
	-e 's,/[^/]*$,,' \
	-e 's,^GNOME/,,' \
	-e 's,^KDE/,,' \
	-e 's,^X\.Org/,,' \
	-e 's,^X11/,,' | \
tr / ' ' | \
sort -u

- Barry
  Disclaimer: Statements made herein are not made on behalf of NIAID.


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple