Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Date:	Tue, 24 Sep 2002 09:47:18 +1000 (EST)
From:	luke DOT kendall AT cisra DOT canon DOT com DOT au
Subject:	Questions about Cygwin packaging
To:	cygwin AT cygwin DOT com
MIME-Version:	1.0
Message-Id:	<20020923234719.2B07B575B@ivory.research.canon.com.au>

I briefly considered making a proper package for a couple of things for
Cygwin, but after reading http://www.cygwin.com/setup.html I realised I
didn't know how to provide the required information.

The issues were package names, and dependencies.

How do you determine package names for the "required:" line
when you're trying to do the right thing and package stuff up
for inclusion in Cygwin.

For example, what is the package name for X11?  Is it "X" or "X11",
"X11R6", or "XFree86".  What about normal system dependencies like
cygwin.dll - what is their package name?

How do you find out what the set of valid package names is?  How do you
create new ones when needed?

BTW, is it possible to run some utility that would automatically tell
you what packages a utility depended on?

How accurate do the package names have to be?  Are they used in
some automated process, or are they just rough guides for humans
to see?

luke


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -