From mboxrd@z Thu Jan  1 00:00:00 1970
Return-path: <ptxdist-bounces@pengutronix.de>
Received: from ptx.hi.pengutronix.de ([2001:67c:670:100:1d::c0]
	ident=Debian-exim) by metis.ext.pengutronix.de with esmtp (Exim 4.72)
	(envelope-from <mol@pengutronix.de>) id 1YZJJS-00028G-4b
	for ptxdist@pengutronix.de; Sat, 21 Mar 2015 14:19:38 +0100
Received: from mol by ptx.hi.pengutronix.de with local (Exim 4.80)
	(envelope-from <mol@pengutronix.de>) id 1YZJJS-0000so-2y
	for ptxdist@pengutronix.de; Sat, 21 Mar 2015 14:19:38 +0100
Date: Sat, 21 Mar 2015 14:19:38 +0100
From: Michael Olbrich <m.olbrich@pengutronix.de>
Message-ID: <20150321131938.GI20453@pengutronix.de>
References: <916A03CCEB30DF44AD98D4CFDC7448D02AA987B2@nooslzsmx1.zenitelcss.com>
	<e1ac548ab568adf1a26f35cfb235fe1d@localhost>
	<916A03CCEB30DF44AD98D4CFDC7448D02AA9881F@nooslzsmx1.zenitelcss.com>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <916A03CCEB30DF44AD98D4CFDC7448D02AA9881F@nooslzsmx1.zenitelcss.com>
Subject: Re: [ptxdist] Rule execution order
Reply-To: ptxdist@pengutronix.de
List-Id: PTXdist Development Mailing List <ptxdist.pengutronix.de>
List-Unsubscribe: <http://metis.pengutronix.de/cgi-bin/mailman/options/ptxdist>, 
	<mailto:ptxdist-request@pengutronix.de?subject=unsubscribe>
List-Archive: <http://metis.pengutronix.de/pipermail/ptxdist>
List-Post: <mailto:ptxdist@pengutronix.de>
List-Help: <mailto:ptxdist-request@pengutronix.de?subject=help>
List-Subscribe: <http://metis.pengutronix.de/cgi-bin/mailman/listinfo/ptxdist>, 
	<mailto:ptxdist-request@pengutronix.de?subject=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 Wed, Mar 04, 2015 at 10:28:08AM +0000, Alan Martinovic wrote:
> >All? Also through applications not using git or built from tarballs?
> 
> Nope, just for the custom apps.
> 
> >What about making this package depending on all the packages you collect this information from?
> 
> So far, I've only seen 'select' in KConfig behave the correct way (by that I
> mean actually forcing the execute in correct order).
> 'depends' only influenced the availability in menuconfig.
> However, using 'select' is two rigid because not all custom applications need
> to be selected for a build.

You can do more or less the same manually. Just add to each package 'foo'
something like this:

ifdef PTXCONF_FOO
$(STATEDIR)/bar.prepare: $(STATEDIR)/foo.install
endif

Michael

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