From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail-la0-x230.google.com ([2a00:1450:4010:c03::230]) by metis.ext.pengutronix.de with esmtp (Exim 4.72) (envelope-from ) id 1W0xMy-0006tT-8V for ptxdist@pengutronix.de; Wed, 08 Jan 2014 18:56:45 +0100 Received: by mail-la0-f48.google.com with SMTP id n7so1371794lam.7 for ; Wed, 08 Jan 2014 09:56:37 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <7b9f505c08f5635b7ea7dd90cc41ce89@idefix.lespocky.dyndns.org> References: <52CCE8A8.8070906@lespocky.de> <7b9f505c08f5635b7ea7dd90cc41ce89@idefix.lespocky.dyndns.org> Date: Wed, 8 Jan 2014 12:56:37 -0500 Message-ID: From: Jon Ringle Subject: Re: [ptxdist] git ptxdist best practices Reply-To: ptxdist@pengutronix.de List-Id: PTXdist Development Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0011565265==" Sender: ptxdist-bounces@pengutronix.de Errors-To: ptxdist-bounces@pengutronix.de To: ptxdist@pengutronix.de --===============0011565265== Content-Type: multipart/alternative; boundary=001a11c38892de932604ef7936b3 --001a11c38892de932604ef7936b3 Content-Type: text/plain; charset=ISO-8859-1 On Wed, Jan 8, 2014 at 4:21 AM, Alexander Dahl wrote: > Hei hei, > > Am 2014-01-08 07:12, schrieb Jon Ringle: > > On Wed, Jan 8, 2014 at 12:56 AM, Alexander Dahl > wrote: > >> This is exactly what we do, alas we do not use any ptxdist magic but two > >> self written shell scripts residing in another git repository "scripts" > >> included as submodule. Our rules/foo.make use one script for the get and > >> one for the extract stage. Those scripts make are called with two extra > >> variables from rules/foo.in as parameter. For each of our own packages > >> those describe clone path and which git entity (branch, tag, changeset) > >> to checkout after cloning. All these packages are cloned to > >> local_src/foo and build with cmake in local_src/foo-git. I assume all > >> this specific to our needs, but that's the way we do it. If you're > >> interested in the scripts, tell me. > >> > >> > > Yes, I would be interested to see your scripts and how you use them in > your > > *.make and *.in :) > > Okay I edited them a little and attached it. Note: the scripts itself > are put in a subfolder of the BSP here named "scripts". > > I decided to use the get stage for cloning a git repo or checking if > it's correctly cloned and if fetching all branches and changesets > without updating the working copy at this stage. The other script for > the extract stage does the actual checkout then. It works. ;-) > > Thanks! How do you deal with creating a rule/kernel.make file that does this if I build Linux using my own tag? It seems that kernel may need some special handling Jon --001a11c38892de932604ef7936b3 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On W= ed, Jan 8, 2014 at 4:21 AM, Alexander Dahl <post@lespocky.de>= wrote:
Hei hei,

Am 2014-01-08 07:12, schrieb Jon Ringle:
> On Wed, Jan 8, 2014 at 12:56 AM, Alexander Dahl <= post@lespocky.de> wrote:
>> This is exactly what we do, alas we do not= use any ptxdist magic but two
>> self written shell scripts residing in another git repository &quo= t;scripts"
>> included as submodule. Our rules/foo.make use one script for the g= et and
>> one for the extract stage. Those scripts make are called with two = extra
>> variables from rules/f= oo.in as parameter. For each of our own packages
>> those describe clone path and which git entity (branch, tag, chang= eset)
>> to checkout after cloning. All these packages are cloned to
>> local_src/foo and build with cmake in local_src/foo-git. I assume = all
>> this specific to our needs, but that's the way we do it. If yo= u're
>> interested in the scripts, tell me.
>>
>>
> Yes, I would be interested to see your scripts and how you use them in= your
> *.make and *.in :)

Okay I edited them a little and attached it. Note: the scripts itself=
are put in a subfolder of the BSP here named "scripts".

I decided to use the get stage for cloning a git repo or checking if
it's correctly cloned and if fetching all branches and changesets
without updating the working copy at this stage. The other script for
the extract stage does the actual checkout then. It works. ;-)

Thanks!

How do you deal with creating a rule/k= ernel.make file that does this if I build Linux using my own tag? It seems = that kernel may need some special handling

Jon
=A0


--001a11c38892de932604ef7936b3-- --===============0011565265== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline -- ptxdist mailing list ptxdist@pengutronix.de --===============0011565265==--