Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm Sender: cygwin-apps-owner AT cygwin DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Mail-Followup-To: cygwin-apps AT cygwin DOT com Delivered-To: mailing list cygwin-apps AT cygwin DOT com Message-ID: <3CB393D6.4030405@ece.gatech.edu> Date: Tue, 09 Apr 2002 21:22:30 -0400 From: Charles Wilson User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2 X-Accept-Language: en-us MIME-Version: 1.0 To: Robert Collins CC: Ian Burrell , cygwin-xfree AT cygwin DOT com, cygwin-apps AT cygwin DOT com Subject: Re: info: single install xfree86 + minimal cygwin? References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Robert Collins wrote: >>They were simple changes to the script I wrote to repackage the >>distributed archives. I'll try to write proper setup.hint >>files for all >>the packages. >> > > Cool. I'm unclear about how the -src packages (are/should be) handled, since there are a great many "binary" packages in XFree, but only a few original "source" packages. In the past, when multiple "binary" packages are generated from a single "source" package, we've done the following: ncurses-5.2-?-src.tar.bz2 contains the actual src dist for ncurses/libncurses, with cygwin patches, build scripts, etc However, building this -src generates two "binary" packages: ncurses-5.2-?.tar.bz2 libncurses6-5.2-?.tar.bz2 So, we create an empty libncurses6-5.2-?-src.tar.bz2 that contains only a single README that says "go look over there, in ncurses-5.2-?-src.tar.bz2". Now, this works, and upset/setup are happy (every binary package has a "src" package) but it is hackish, ugly, and a pain to maintain. Is there a better solution? (Or can we discard the psuedo-src packages without repurcussion? Won't upset be upset by the "bin without src" problem?) --Chuck