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=W+i5ggiJJUZW2HuHJqMr4yP2jIZf00UzzfWJDizPxWUhQE1WZ28TQ NcGoX5v/VuUUj1QJBjQkc1K7iaGudoS4mX8MLug8ODkYNRrNQtxfnAPmLyyLNetL gBkGkyxXgENT6RzWtmWKqfcD6el4dr3pnhBLtw/hgKlNMoXQueISEo= 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=MKoWRuKDQXOIKr/DlbDIVYVOTis=; b=x68QQCHNIFzEWH7mvv3gHQsuWK+O AwO0s/wVOVwYg8fVgvAI1AVqbjNS+G9bSaIJJ3ICWKj2br6J4oQa9zJCE6zXufHl lQEJdQs/QcJAiKo6RX22nReWnMpBWfs2D/cpRNvrX7UIOUgEFWepKD4ei8Sm05GQ RfbIqtNJ55pgDXM= 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=1.0 required=5.0 tests=BAYES_20,KAM_LAZY_DOMAIN_SECURITY autolearn=no version=3.3.2 spammy=installeddb, installed.db, postinstall, preremove X-HELO: blaine.gmane.org To: cygwin AT cygwin DOT com From: Andrew Schulman Subject: Re: Manual installation of cygport packages Date: Tue, 21 Mar 2017 10:45:17 -0400 Lines: 34 Message-ID: References: <87fuid3vex DOT fsf AT Rainer DOT invalid> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive: encrypt X-IsSubscribed: yes > Andrew Schulman writes: > >> On 3/15/2017 6:37 AM, Rui Pedro Caldeira wrote: > >> > 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. > > You should also generate the compressed packges listing in /etc/setup > and an entry into the installed.db file or you will be unable to > properly un-install the package later on. The only time I'm using this > manual installation is when I quickly need to test an update on an > already installed package that I will later re-install properly via the > local package repository. Of course if these need postinstall actions > you also need to run those, so this quickly gets more complicated than > having setup do its thing. Maybe. But for most packages that I unpack this way to test, (1) the package is already installed or I'm going to adopt it anyway, so I'll end up installing it properly using setup, which will take care of other setup like installed.db; and (2) the preremove and postinstall scripts either do nothing or do only trivial things like updating config files. So for most cases, it works just fine just to unpack the archive into the root file system in order to test it. -- 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