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: List-Archive: List-Post: List-Help: , Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com Date: Fri, 23 Nov 2001 17:37:37 -0500 From: Christopher Faylor To: cygwin-apps AT cygwin DOT com Subject: Re: Remove cinstall src directory from snapshots Message-ID: <20011123223737.GA28560@redhat.com> Reply-To: cygwin-apps AT cygwin DOT com Mail-Followup-To: cygwin-apps AT cygwin DOT com References: <20011122023613 DOT GA8976 AT redhat DOT com> <03f501c1732c$21f2a570$0200a8c0 AT lifelesswks> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <03f501c1732c$21f2a570$0200a8c0@lifelesswks> User-Agent: Mutt/1.3.23.1i On Thu, Nov 22, 2001 at 07:03:11PM +1100, Robert Collins wrote: >----- Original Message ----- >From: "Christopher Faylor" > > >> How should the sources for utils and cinstall be distributed? >> >> I have just managed to separate winsup/utils as a separate binary >> release but I'm not 100% certain how to release the sources. >> >> winsup/utils is pretty useless without the cygwin directories, I >think. >> It can probably get by with the installed mingw/w32api, though. >> >> So, I'm not sure how to release utils. Maybe I need to separate out >> the parts of cygwin that get used by utils and put it in a separate >> directory. > >I don't think so, there's no reason that the source for utils isn't >cygwin-1.5.3-1-src.tar.bz2. I thought of that but then I'd have to release a version of cygwin sources with winsup/utils that had no relationship to the net release. Maybe that's not a problem. You don't think we'd have people trying to build cygwin itself from these sources? In the RPM world, there would be one set of sources which produced two different binary RPMs, however, the binaries would be in lock step like they currently are wrt cygwin1.dll and all of the cygwin utils. >> I know that Robert has a plan for this but maybe this is as simple as >> just including a tar ball next to setup.exe at sources.redhat.com. > >That sounds fine to me. Or a link to the CVS page and a note there that >cinstall is the setup.exe sources. > >IIRC the GPL doesn't prevent CVS being the distribution method as long >as its under the distributors control. Right. I think that we'd have to tag each release, though, just to be nice. Sounds good to me. cgf