From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 130015 invoked by alias); 7 Apr 2016 12:03:16 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 130005 invoked by uid 89); 7 Apr 2016 12:03:15 -0000 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 Received: from mail-wm0-f54.google.com (HELO mail-wm0-f54.google.com) (74.125.82.54) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-GCM-SHA256 encrypted) ESMTPS; Thu, 07 Apr 2016 12:03:05 +0000 Received: by mail-wm0-f54.google.com with SMTP id 191so89159890wmq.0 for ; Thu, 07 Apr 2016 05:03:05 -0700 (PDT) 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) Received: from dinwoodie.org ([2001:ba8:0:1c0::9:1]) by smtp.gmail.com with ESMTPSA id wr2sm8152351wjc.49.2016.04.07.05.03.01 for (version=TLS1_2 cipher=AES128-SHA bits=128/128); Thu, 07 Apr 2016 05:03:01 -0700 (PDT) Date: Thu, 07 Apr 2016 12:03:00 -0000 From: Adam Dinwoodie To: cygwin@cygwin.com Subject: Re: How can I try a newly build package locally? Message-ID: <20160407120259.GC2345@dinwoodie.org> References: <1459893529576-126009.post@n5.nabble.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) X-IsSubscribed: yes X-SW-Source: 2016-04/txt/msg00138.txt.bz2 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 ` 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