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:content-type:mime-version:subject:from
	:in-reply-to:date:content-transfer-encoding:message-id
	:references:to; q=dns; s=default; b=vkWa3ncfcTvBxE4vQ0l/OVagkrdJ
	SRTiSyqSXIm4EVVYnwICVxPjjLOv3wuiFCWhHvUZnPqkBo5/NfBS0rU3XusCVfEu
	I3qFPdqkuL/Wqw3yEcSPMdBwVNs5XJ0vdiF5bYiAYqzQb+Cr8xnaHTpAoVv0yUrA
	WxWZaRtKorj2U2k=
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:content-type:mime-version:subject:from
	:in-reply-to:date:content-transfer-encoding:message-id
	:references:to; s=default; bh=VNr7CoFV8p7BR1WVgvdumBZwn2M=; b=i7
	KCcgpxBS1LnqmpP4xtDTTZylp6mtR0ZDsdbZWIrzntMyudrcPTvK1csrS0ND0ZZk
	Xb5FYhUeA30lE86jO3ENJpqvFL74Jg6gDkVfAUg94lryt1/F0fFUORAh7evyBKnv
	XlLd7NAuYCkSWYQqmFCeDn/6QLq6EgcWpFNTtQjSs=
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=2.8 required=5.0 tests=AWL,BAYES_00,BODY_8BITS,GARBLED_BODY,T_RP_MATCHES_RCVD autolearn=no version=3.3.2
X-HELO: etr-usa.com
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
Subject: Re: How to verify a cygport package
From: Warren Young <wyml AT etr-usa DOT com>
In-Reply-To: <CAFSLk9fP0YeKUyYQT2eNqhP-oZ5bFPSu3S6=AOED6krf+bBHdg@mail.gmail.com>
Date: Fri, 30 Jan 2015 11:19:22 -0700
Message-Id: <7AE758B5-8CF2-4E8E-BEB4-CA20A5CA6392@etr-usa.com>
References: <CAFSLk9fP0YeKUyYQT2eNqhP-oZ5bFPSu3S6=AOED6krf+bBHdg AT mail DOT gmail DOT com>
To: The Cygwin Mailing List <cygwin AT cygwin DOT com>
X-IsSubscribed: yes
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id t0UIKvMY015369

> On Jan 29, 2015, at 8:24 PM, 陳韋任 <chenwj.cs97g+cygwin AT g2 DOT nctu DOT edu DOT tw> wrote:
> 
> However, `cygport install` doesn't "install" the package just created
> (apparently I misunderstand what it does).

cygport is not a package manager.  It is a package *creator*, only.

“cygport install” is basically a wrapper around “make install” in your build tree.  Because cygport was supposed to set up the build system to install into a private installation tree underneath your cygport build tree, the resulting files won’t end up in /usr/bin and such.  They’ll be in a subdirectory of the one containing the *.cygport file.

>  What should I do to make sure the package works? Thanks.

After “cygport install” say “cygport package” to create the tarball.

Then:

    $ tar tvf package.tar.xz
    (check that it looks sane)
    $ cd /
    $ tar xvf /path/to/package.tar.xz
    (use package; is everything fine?)

Finally, submit ITP message per http://cygwin.com/setup.html
--
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