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: <3D0407A8.6090102@ece.gatech.edu> Date: Sun, 09 Jun 2002 21:58:00 -0400 From: Charles Wilson User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2 X-Accept-Language: en-us MIME-Version: 1.0 To: quetschke AT scytek DOT de CC: cygwin-apps AT cygwin DOT com Subject: Re: package offering: gnupg References: <3D02D765 DOT 8010202 AT ece DOT gatech DOT edu> <20020609113456 DOT A754923 AT MILAMBER> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit quetschke AT scytek DOT de wrote: > Hi! > > >>>I'd prefer the re-autotool stuff to be part of the user build process. >>>I was going to propose this for ImageMagick, as it reduces the patches >>>from approx 1 Mb down to 2 lines. Much easier to understand. >>> > This was my intention as I put the auto* part in the gnupg-1.0.7-1.sh, but > my question is, if I do it this way, do I have to put autoconf and automake > in the setup.hint requires line? > > I mean, do all the packages required to build from source have to be put > in setup.hint? Right now this is not the case in the gnupg package. Nope. We don't (yet) have a "build-requires" facility in hints/setup.exe. The only stuff that goes in the requires: line are those things that the *end user* would need -- not a developer who wishes to rebuild your package from source. --Chuck