Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com X-Authentication-Warning: localhost.localdomain: ronald set sender to blytkerchan AT users DOT sourceforge DOT net using -f Date: Mon, 11 Aug 2003 16:13:06 +0200 From: Ronald Landheer-Cieslak To: Sven =?iso-8859-1?Q?K=F6hler?= Cc: cygwin AT cygwin DOT com Subject: Re: how to become a package maintainer? Message-ID: <20030811141306.GB10319@linux_rln.harvest> Reply-To: cygwin AT cygwin DOT com References: Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.4i X-Disclaimer: I had nothing to do with it - I swear! X-loop: linux_rln.harvest I'm pretty sure you'll be welcome among the packaging crew. All you have to do to become a packager is: * subscribe to cygwin-apps at cygwin dot com * propose the package (i.e. write a mail with subject [ITP] libvorbis and in the contents what libvorbis is (don't expect us to know even though we do most of the time) where to find the canonical version, and why you'd like to see it in the distro. * wrap up the package (read http://cygwin.com/setup.html) * propose somewhere for the other packagers to download your package to test it * wait for votes and hope there's no veto * wait for reviews and fix whatever needs fixing. On Mon, Aug 11, 2003 at 03:33:32PM +0200, Sven Köhler wrote: > - how to install files with "make install" in another directory than > root? i don't want to select all the files that belong to binary package > by hand. ./configure --prefix=/usr make install DESTDIR=/path/to/destdir you probably won't need any of this if you use method 2 for packaging and this will of course only work if the Makefile and configury support it. > - how do i build DLLs? i could compile libao, libogg and libvorbis but i > only get *.la and *.a files but no *.dll like i would expect. i thought > that this would be managed by autoconf/configure somehow, but it isn't > as it seems. It's managed by libtool, but you may have to re-libtoolize. If the packs are not libtoolized, you'll have to tamper with the Makefile and/or configury to get it done. In any case, if you need more specific help, you'll need to ask more specific questions *here* at cygwin proper. HTH rlc -- "The IETF motto is 'rough consensus and running code'" -- Scott Bradner (Open Sources, 1999 O'Reilly and Associates) -- 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/