[ptxdist] Rule execution order

[ptxdist] Rule execution order

[Alan Martinovic]

[-- Attachment #1.1: Type: text/plain, Size: 773 bytes --]

Hi,
how to enforce that a rule is executed last before the rootfs is built?

Motivation:
I have a script that goes through all the application sources runs "git describe --tags" and maps that to the app name.
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.

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.

[-- Attachment #1.2: Type: text/html, Size: 2600 bytes --]

[-- Attachment #2: Type: text/plain, Size: 48 bytes --]

-- 
ptxdist mailing list
ptxdist@pengutronix.de

Re: [ptxdist] Rule execution order

[Alexander Dahl]

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

-- 
ptxdist mailing list
ptxdist@pengutronix.de

Re: [ptxdist] Rule execution order

[Alan Martinovic]

>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

Re: [ptxdist] Rule execution order

[Michael Olbrich]

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