From mboxrd@z Thu Jan  1 00:00:00 1970
Return-path: <ptxdist-bounces@pengutronix.de>
Received: from dude02.hi.pengutronix.de ([2001:67c:670:100:1d::28]
 helo=dude02.lab.pengutronix.de)
 by metis.ext.pengutronix.de with esmtps
 (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92)
 (envelope-from <mol@pengutronix.de>) id 1hiaFZ-0003rK-6E
 for ptxdist@pengutronix.de; Wed, 03 Jul 2019 10:04:21 +0200
Received: from mol by dude02.lab.pengutronix.de with local (Exim 4.89)
 (envelope-from <mol@pengutronix.de>) id 1hiaFY-0007Vp-UT
 for ptxdist@pengutronix.de; Wed, 03 Jul 2019 10:04:20 +0200
Date: Wed, 3 Jul 2019 10:04:20 +0200
From: Michael Olbrich <m.olbrich@pengutronix.de>
Message-ID: <20190703080420.gkeerqnu5xtw2plk@pengutronix.de>
References: <2551525.rF1KUiLOMo@dabox>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <2551525.rF1KUiLOMo@dabox>
Subject: Re: [ptxdist] Mitigate build stamp disadvantages for local_src
 packages
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/cgi-bin/mailman/private/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>
Reply-To: ptxdist@pengutronix.de
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ptxdist-bounces@pengutronix.de
Sender: "ptxdist" <ptxdist-bounces@pengutronix.de>
To: ptxdist@pengutronix.de

Hi,

On Wed, Jul 03, 2019 at 08:58:54AM +0200, Tim Sander wrote:
> I have noticed that in yocto which is also basically build stamp based that 
> local cmake projects get build when they are not updated. So i am wondering if 
> something like this would be also possible with ptxdist?
> 
> This is one of the most observed errors after a git pull...

'...get build when they are not updated.'? This makes no sense to me. Is
the 'not' correct here? If not then I assume you want to automatically
rebuild local_src packages when the code changes.

There is no integrated solution for this, but it's all make dependencies,
so you can implement something yourself.
If the local_src package has a separate git repository, then you could add
a dependency like this:

$(STATEDIR)/<pkg>.<commitish>.githash:
	rm $(STATEDIR)/<pkg>.*.githash
	touch $@

$(STATEDIR)/<pkg>.prepare: $(STATEDIR)/<pkg>.<commitish>.githash

and generate the commitish with
$(call ptx/force-sh,git -C <dir> rev-parse HEAD)
or something like that.

I'm open to ideas on howto integrate this better. Maybe track
$(<PKG>_VERSION) changes. The you could add the appropriate shell code
there to generate some version string.
Hmm, maybe some helper macro to generate a useful version.

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