From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 330 invoked by alias); 5 Sep 2011 15:39:15 -0000 Received: (qmail 321 invoked by uid 22791); 5 Sep 2011 15:39:13 -0000 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 Received: from nihxway5out.hub.nih.gov (HELO nihxway5out.hub.nih.gov) (128.231.90.113) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 05 Sep 2011 15:38:59 +0000 X-IronPortListener: Outbound_SMTP X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AqIAANXrZE6cKEdK/2dsb2JhbABDmFOPRXiBRgEBAQEDEig4FwIBCA0nAhAfEyUBAQQBGhqkMptThgpgBItyjGmLfA Received: from unknown (HELO NIHHTRC.nih.gov) ([156.40.71.74]) by nihxway5out.hub.nih.gov with ESMTP; 05 Sep 2011 11:38:57 -0400 Received: from NIHMLBX02.nih.gov ([156.40.71.32]) by NIHHTRC.nih.gov ([156.40.71.74]) with mapi; Mon, 5 Sep 2011 11:38:58 -0400 From: "Buchbinder, Barry (NIH/NIAID) [E]" To: 'Luke Kendall' , "cygwin@cygwin.com" Date: Mon, 05 Sep 2011 15:39:00 -0000 Subject: RE: More on Cygwin package naming Message-ID: <0105D5C1E0353146B1B222348B0411A20A23D32202@NIHMLBX02.nih.gov> References: <4E643ED8.3030100@cisra.canon.com.au> In-Reply-To: <4E643ED8.3030100@cisra.canon.com.au> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com X-SW-Source: 2011-09/txt/msg00036.txt.bz2 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=20 >"package" seems to refer to each .tar.bz2 file (for the source and=20 >install files of each version). So perhaps I should instead be talking=20 >about "@-names" - the name that appears after an "@" in setup.ini. > >Anyway, this is all related to me trying to determine the licenses for=20 >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=20 >happen when a parent Freshmeat project is split into several cygwin=20 >"@-named" pieces: in that situation, I can't find any automatable way to=20 >tie the child names back to the parent. E.g. libncurses9 is a cygwin=20 >item from within the ncurses freshmeat project; or libintl,=20 >libintl{2,3,8} in cygwin, which are all part of the gettext project on=20 >Freshmeat. Currently I'm resorting to human inspection. > >I'd love to know if there's some way to determine this kind of=20 >parent-child relationship. Is there some setup.hint or upset or genini=20 >file or info lurking around (where?) that I could scrape such=20 >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 bf501b5= 40c768d63358426686c615530 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