X-Recipient:	archive-cygwin AT delorie DOT com
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=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; 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; s=default; bh=yUQ+kT80er7eNPZP5OmZ8VLt1+w=; b=osdn
	sQMqPG8mSGG58aSCnGkLHvlhPol/jOm4Y5uYi6mH7rUHi9P+N/lwiT+T9ldBEoap
	mqDOZxSO6RRfkGokFOsmZaGOzDH7AIisORMshVn6SBf9uklryc+Fhr4uHLkXdO49
	/6dQ578wgq5E6e6jiaWRj6qf45EzYoZbrJmCozk=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=-0.7 required=5.0 tests=BAYES_40,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy=tarballs, tarball, installer, bz2
X-HELO:	mail-wm0-f54.google.com
X-Google-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:subject:message-id:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to:user-agent; bh=olJ5A/Np4+I1Z0Yd0OJijrlGgkrDSOeW9elSYCsyoyY=; b=emkfrG6pCM3WsqTqX2/cNaj6zqSWtN6Y3dEnT2GLf+SL5ncDwYy33dcvEIP1WRf3HD 1yqmRlr2wcaztY1itACfdx5b/glSIApviKpU3IOrAWBRRdfIdwQ3zhq4JcxIPJ9R1IAn Q8qB4JD7lsS+ae9wXY/m9cXfURFCS5H1SmeiWeORkJZz26SMdvuKWWbioPzNrp3q3ws0 RInLSfZZT3+lA7jHLc48RqmPKLvdtH4A8IbVZIodK/VIIWpWRo2xP63IS34wLMfIPEM7 Dq1AH+a0IhsWDK41rIkadBUxDYP+RYEikB/vlIlPt2VXt1sb1gU0nbHZ/jJcc2eQs3Zh mrDQ==
X-Gm-Message-State:	AD7BkJK6fGTEV2f22gWxeU/S/8XVFOfhWAYZ2njBhPw9J8UtlnH7+0lJGXS1swAZHhgxLQ==
X-Received:	by 10.28.125.2 with SMTP id y2mr3673201wmc.90.1460030582550; Thu, 07 Apr 2016 05:03:02 -0700 (PDT)
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
In-Reply-To:	<1459893529576-126009.post@n5.nabble.com>
User-Agent:	Mutt/1.5.21 (2010-09-15)
X-IsSubscribed:	yes

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

- Raw text -