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:mime-version:references:in-reply-to:from:date
	:message-id:subject:to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=jIIM3BBX4qKTUNygpyC5J2161tRTe97ZU0KFx3KMBa0
	HqgWLvxWYahsYl4Q+jDrsAZrgJ6lV0REHqDHwCPrvvhiDlKukGeVDcWv8F1YXSwl
	FSRJ1/LPUn+726JOtjFykSEOd2iYsYLTa9HzCgiVIcNwgrxshG2cwjhO2IUccffw
	=
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:mime-version:references:in-reply-to:from:date
	:message-id:subject:to:content-type:content-transfer-encoding;
	 s=default; bh=gWhln0iC2doBDiYaB4SRvIynlMQ=; b=p+6Z5Bm0J2kZYqWA+
	ESXv9PvPLaJO/cd9K+loR8yStF7Z5nrmTZcSCfVevyRWJTpXA04LvMenLID1xfdD
	20ZjZtKU8FG+msZ92GN30JyzwfjifGfeZ1ZxNFzDY1Tustz/ubrazz9aEui1PhGF
	AKWVczwWNnldgO3es5jBdQkIpg=
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-Spam-SWARE-Status: No, score=-1.7 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.1 spammy=subdirectory, dinwoodieorg, UD:dinwoodie.org, dinwoodie.org
X-HELO: mail-ua1-f48.google.com
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;        d=dinwoodie.org; s=google;        h=mime-version:references:in-reply-to:from:date:message-id:subject:to         :content-transfer-encoding;        bh=P9sh7gm0vcdEz7f+yYyFbd1VJA3yUqeObCpM6Py1BxM=;        b=fRV1V6M3nM35bv51yBIIJe3L0HMrCUjCyV7NKBstQRP4OaO5dZ/M0BBp7WOdVh82/e         Iq3S68VsiRUFaj5IU/+APFFz8XZ0Nz55DCcDv//4ktyVK0tbvwcv6AcLuWczS2u9UdVE         8EVc/XpobRNJ2IENNRiu2Zqpua1CPUN3tUCn4=
MIME-Version: 1.0
References: <0F7D3B1B3C4B894D824F5B822E3E5A178FD5F8F7 AT IRSMSX102 DOT ger DOT corp DOT intel DOT com>
In-Reply-To: <0F7D3B1B3C4B894D824F5B822E3E5A178FD5F8F7@IRSMSX102.ger.corp.intel.com>
From: Adam Dinwoodie <adam AT dinwoodie DOT org>
Date: Wed, 1 May 2019 23:35:44 +0100
Message-ID: <CA+kUOak-kpRv9+AEnxncNRAKyRsv1vN6HTnZXLNS6z6weKqFOg@mail.gmail.com>
Subject: Re: Does "cygport <cygport-file> install" actually install a compiled package?
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset="UTF-8"
X-IsSubscribed: yes
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id x41MaXnG019915

On Wed, 1 May 2019 at 22:43, Soegtrop, Michael wrote:
> I compiled a package using cygport <package.cygport> all. According to the documentation this should also install the package, but I don't see the files in my local installation updated. Is this a misunderstanding of what "install" means in this context or do I miss some command line options? cygport <package.cygport> install also seems to create the packages, but doesn't install anything as far as I can tell.

Yes, you're misunderstanding the intent of "cygport <package>
install". That command install the package into a temporary
subdirectory so that a subsequent "cygport <package> pack" can package
up the contents of the subdirectory to get all the installed files and
only the installed files by just bundling up the entire directory
contents. It's not intended to install anything so that it's available
for direct use in your local environment.

Cygport is a packaging tool, not an installation tool, and I'm not
sure there's a simple way to make it install a package into your
system directories so it can be used by a regularly installed package.
The best thing I can think of is to run the "cygport <package> pack"
command, find the tarballs that command will create, then unpack those
tarballs with "tar -xa -C / -f <tarball>"; that'll work for most
packages, although I suspect it won't work as expected for things that
have post-install scripts.

Adam

--
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