From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from octopus.hi.pengutronix.de ([2001:6f8:1178:2:215:17ff:fe12:23b0]) by metis.ext.pengutronix.de with esmtp (Exim 4.72) (envelope-from ) id 1RHhaX-0006tX-Lv for ptxdist@pengutronix.de; Sat, 22 Oct 2011 21:50:37 +0200 Received: from rsc by octopus.hi.pengutronix.de with local (Exim 4.76) (envelope-from ) id 1RHhaX-0008Dk-Kn for ptxdist@pengutronix.de; Sat, 22 Oct 2011 21:50:37 +0200 Date: Sat, 22 Oct 2011 21:50:37 +0200 From: Robert Schwebel Message-ID: <20111022195037.GX7130@pengutronix.de> References: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: Subject: Re: [ptxdist] How to update another packet at install Reply-To: ptxdist@pengutronix.de List-Id: PTXdist Development Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: ptxdist-bounces@pengutronix.de Errors-To: ptxdist-bounces@pengutronix.de To: ptxdist@pengutronix.de On Sat, Oct 22, 2011 at 03:24:33PM -0400, Jon Ringle wrote: > Create a rules/.postinst > The .postinst script will get called at targetinstall phase > during building, so you probably want to have your script do nothing > at this time. The way I handled this is that "configure" will be $1 > when the packet is installed on the target. This is my template for > .postinst: You can use $DESTDIR to detect if you are running at targetinstall or on runtime. rsc -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | -- ptxdist mailing list ptxdist@pengutronix.de