DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:references
	:mime-version:content-type:content-transfer-encoding
	:in-reply-to; q=dns; s=default; b=js0brfw4ZWrcEwnuBT3UeDarBu7cqs
	lCZr5gHR3UCnNM/p05cYuU31m1kOyQx7A6EofA9Oziw54FtWrF5J1YeSkRNA7MO1
	C+g5SqEeZi6XM28mtsHGuKrxZxr6Fr8jXuYhYu6RIo5cYSaQatD/lnQFROaAfUgQ
	bUn3H61MD60R4=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Date: Thu, 7 Apr 2016 13:02:59 +0100
From: Adam Dinwoodie <adam AT dinwoodie DOT org>
To: cygwin AT cygwin DOT com
Subject: Re: How can I try a newly build package locally?
Message-ID: <20160407120259.GC2345@dinwoodie.org>
References: <1459893529576-126009 DOT post AT n5 DOT nabble DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <1459893529576-126009.post@n5.nabble.com>
User-Agent: Mutt/1.5.21 (2010-09-15)

On Tue, Apr 05, 2016 at 02:58:49PM -0700, thoni56 wrote:
> I'm a maintainer of a program that I'd might like to propose for inclusion in
> the Cygwin distribution.
> 
> We use CMake so there is a packager available, and it's easy to create a
> .bz2 package.
> 
> Once I've created the package, how can I try it locally? In Linux this can
> easily be done with dpkg, but is there a way to use the Cygwin package
> installer so that it picks up a local package?
> 
> I've read [the package contribution documentation][1] and related pages but
> can't find an answer.
> 
> /Thomas
> 
>   [1]: https://cygwin.com/setup.html

Cygwin packages generally use Cygport to define the build process and so
forth.  It's more-or-less the equivalent of rpmbuild for RPM packages,
and similar tools for other distribution systems.  The documentation for
Cygport is at http://cygwinports.github.io/cygport/; if you're using
make in a reasonably standard way, most things should Just Work™.

In particular, if you're using Cygport, it'll automatically do things
like creating setup.hint files for you.

For testing locally, I find it's simplest to just do `tar -xaC/ -f
<tarball>` on the compiled tarballs that Cygport generates.  That
doesn't test the dependency management or anything that requires
post-install scripts, but it's fine for checking the installation itself
works.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple