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:to:from:subject:date:message-id:references :mime-version:content-type:content-transfer-encoding; q=dns; s= default; b=dFPyEn08O7cYU2uw1EPKVYp/9kc6NmwbUphORyRV2+n6IRaKoCFss +MnII6K5sHR4eNPE0BquU+t/yQor1YVx+sig+DG723tEE16rlwv2A/cII06kQE5G G42bMfnhab2ImKxwURUcComroeqgnYagYHUHAdXa2qOfZ87baEX18s= 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:to:from:subject:date:message-id:references :mime-version:content-type:content-transfer-encoding; s=default; bh=T1KX1qKKRIDKgE5zydIUig2Yc/I=; b=dFMdUI/+r3uTg09hXGjopuDNZHAW NH6O2OQYmfO+w0a59T+2yJoQxzF+waZkKuFT9phxdxcIga/ZwWYDXJ0puGsKCSK7 p4aDPHXWT3SGB3heXt0LlkfzNe/fe+I3/l3s+qc8AC1OmNBnV6bur+BV0uwLrouP eK9b7DoirBECflQ= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , 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.9 required=5.0 tests=BAYES_00,KAM_LAZY_DOMAIN_SECURITY autolearn=no version=3.3.2 spammy=H*MI:sk:b10fed8, H*r:Unknown, H*F:D*epa.gov X-HELO: blaine.gmane.org To: cygwin AT cygwin DOT com From: Andrew Schulman Subject: Re: Manual installation of cygport packages Date: Thu, 16 Mar 2017 11:41:21 -0400 Lines: 28 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive: encrypt X-IsSubscribed: yes > >> > Hello all, I'm new to this and I successfully build a package with > >> > cygport. My problem is that, I would like to install it in order to > >> > test if the package was successfully built. Is there anyway to do > >> > that? > >> > >> https://cygwin.com/package-server.html > > > > I usually take the simpler approach of just unpacking the package archive > > into the root filesystem: > > > > tar -C/ -Jxf $package-$version.tar.xz > > > > This doesn't run pre-remove or post-install scripts, but it puts the files > > in place so you can test them. > > @Andrew: Is there a way to run the scripts manually? Sure, you can run them manually. They're unpacked into /etc/preremove/$package.sh and /etc/postinstall/$package.sh. For the preremove script, I guess you should run it before unpacking the archive. You can find it in the package build directory in inst/etc/preremove. I'm quite lazy and don't bother doing this, but if the preremove or postinstall scripts are doing something important, you should do it. Andrew -- 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