mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Alan Martinovic <Alan.Martinovic@zenitel.com>
To: Alexander Dahl <post@lespocky.de>,
	"ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] Rule execution order
Date: Wed, 4 Mar 2015 10:28:08 +0000	[thread overview]
Message-ID: <916A03CCEB30DF44AD98D4CFDC7448D02AA9881F@nooslzsmx1.zenitelcss.com> (raw)
In-Reply-To: <e1ac548ab568adf1a26f35cfb235fe1d@localhost>

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

-----Original Message-----
From: Alexander Dahl [mailto:post@lespocky.de] 
Sent: Wednesday, March 04, 2015 10:28 AM
To: ptxdist@pengutronix.de
Cc: Alan Martinovic
Subject: Re: [ptxdist] Rule execution order

Hei hei, 

Am 2015-03-04 10:03, schrieb Alan Martinovic:
> I have a script that goes through all the application sources runs 
> "git describe --tags" and maps that to the app name.

All? Also through applications not using git or built from tarballs?

> In the end it generates a file mapping the apps with versions, and I'd 
> like to have that app on the image.
> It has to run last to ensure that all the apps have been fetched to 
> the latest version.

What about making this package depending on all the packages you collect this information from?

> DISCLAIMER:
> This e-mail may contain confidential and privileged material for the 
> sole use of the intended recipient. Any review, use, distribution or 
> disclosure by others is strictly prohibited. If you are not the 
> intended recipient (or authorized to receive for the recipient), 
> please contact the sender by reply e-mail and delete all copies of 
> this message.

Am I the intendent recipient? What about all the other readers of this mailing list? How can I ensure they all delete the mail? ;-)

Greets
Alex

--
»With the first link, the chain is forged. The first speech censured, the first thought forbidden, the first freedom denied, chains us all irrevocably.« (Jean-Luc Picard, quoting Judge Aaron Satie)
*** GnuPG-FP: 02C8 A590 7FE5 CA5F 3601  D1D5 8FBA 7744 CC87 10D0 ***

DISCLAIMER:
This e-mail may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply e-mail and delete all copies of this message.
-- 
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2015-03-04 10:28 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 [this message]
2015-03-21 13:19     ` Michael Olbrich

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=916A03CCEB30DF44AD98D4CFDC7448D02AA9881F@nooslzsmx1.zenitelcss.com \
    --to=alan.martinovic@zenitel.com \
    --cc=post@lespocky.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