mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Rule execution order
Date: Sat, 21 Mar 2015 14:19:38 +0100	[thread overview]
Message-ID: <20150321131938.GI20453@pengutronix.de> (raw)
In-Reply-To: <916A03CCEB30DF44AD98D4CFDC7448D02AA9881F@nooslzsmx1.zenitelcss.com>

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

      reply	other threads:[~2015-03-21 13:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-04  9:03 Alan Martinovic
2015-03-04  9:27 ` Alexander Dahl
2015-03-04 10:28   ` Alan Martinovic
2015-03-21 13:19     ` Michael Olbrich [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150321131938.GI20453@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox