Mailing-List:	contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender:	cygwin-apps-owner AT sourceware DOT cygnus DOT com
List-Subscribe:	<mailto:cygwin-apps-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin-apps/>
List-Post:	<mailto:cygwin-apps AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-apps-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/lists.html#faqs>
Delivered-To:	mailing list cygwin-apps AT sources DOT redhat DOT com
Message-ID:	<3B9F659A.7040109@ece.gatech.edu>
Date:	Wed, 12 Sep 2001 09:39:38 -0400
From:	Charles Wilson <cwilson AT ece DOT gatech DOT edu>
User-Agent:	Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.2) Gecko/20010713
X-Accept-Language:	en-us
MIME-Version:	1.0
To:	CA List <Cygwin-Apps AT Cygwin DOT Com>
Subject:	Re: Uploading a package to sources
References:	<3B9E56A3 DOT B2E33F29 AT yahoo DOT com> <3B9F6134 DOT 9FEF49F8 AT yahoo DOT com>

Earnie Boyd wrote:

> Anybody know to where I should scp these packages?
> 
> Anyone know how to go about changing the setup.ini or is that Chris's
> baby?
>


Actually, there's an autoscript that regenerates setup.ini based on the 
files underneath /cygwin.  In the absence of a .hint file in  a given 
directory, I think the script parses the filename of the tarball (not 
the directory name)  So mingw-runtime-<ver>-<rel>.tar.bz2 would cause a 
"mingw-runtime" entry to be created, even if you uploaded it into the 
latest/mingw/ directory.

You probably need to ssh, not scp -- if you're going to create a new 
directory (/latest/mingw-runtime instead of /latest/mingw).  But the path is
sourceware.cygnus.com:/sourceware/ftp/anonftp/pub/cygwin/latest/...

-Chuck

- Raw text -