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
Message-ID: <405C33B3.7EC9B70B@dessent.net>
Date: Sat, 20 Mar 2004 04:06:11 -0800
From: Brian Dessent <brian AT dessent DOT net>
Organization: My own little world...
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Process of Installation?
References: <c3g2a1$98b$1 AT sea DOT gmane DOT org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com

George Hester wrote:

> When I run the setup for Cygwin I go through various dialog boxes to download and install various packages.  All the packages come in as name.tar.bz2 files.  Consider this package:
> 
> http://sourceforge.net/project/showfiles.php?group_id=28862
> 
> The files here are in the form name.tar.gz.  What I did was ungzip the package and recompress it as a bz2 file.  What I'd like to do is use the same sequence of events that Cygwin uses to install the name.tar.bz2 files downloaded from Cygwin setup to install my newly formed bz2 file as I just described.  But I don't know the process (the sequence of events) that Cygwin uses on the bz2 files to install the modules.
> 
> So I am asking what that sequence of events are and if it is possible to "manually" install a package such as the above using the same sequence of events as are used through the Setup interface?  Thanks.


.bz2 and .gz are simply compression types.  They specify nothing about
the content or format contained therein.

Cygwin's setup.exe is designed to install Cygwin packages.  These are
not arbitrary .bz2 files but rather special archives created by the
maintainers in a way that makes them installable by setup.  You cannot
simply point setup at arbitrary tarballs[*] and expect it to work.  If
you want to install the items to which you refer, you will need to
download, unpack, configure, make, and install them yourself, fixing any
issues that come up along the way.  Setup can only work with Cygwin
packages.

[*] Unless of course those files are Cygwin packages, with corresponding
setup.ini files.

Brian

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