From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail-lb0-x22d.google.com ([2a00:1450:4010:c04::22d]) by metis.ext.pengutronix.de with esmtp (Exim 4.72) (envelope-from ) id 1W0mNE-0003Is-JS for ptxdist@pengutronix.de; Wed, 08 Jan 2014 07:12:36 +0100 Received: by mail-lb0-f173.google.com with SMTP id z5so983348lbh.32 for ; Tue, 07 Jan 2014 22:12:10 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <52CCE8A8.8070906@lespocky.de> References: <52CCE8A8.8070906@lespocky.de> Date: Wed, 8 Jan 2014 01:12:10 -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="===============1665075542==" Sender: ptxdist-bounces@pengutronix.de Errors-To: ptxdist-bounces@pengutronix.de To: ptxdist@pengutronix.de --===============1665075542== Content-Type: multipart/alternative; boundary=001a11c281088ec6f904ef6f5fb3 --001a11c281088ec6f904ef6f5fb3 Content-Type: text/plain; charset=ISO-8859-1 On Wed, Jan 8, 2014 at 12:56 AM, Alexander Dahl wrote: > Hei hei, > > On 08.01.2014 03:32, Jon Ringle wrote: > > My initial thought is to create a git repo that holds the ptxconfig files > > and local rules/, and then configure the rules to somehow get the git > repos > > by tag for building (as it seems that there is some sort of support for > > this in scripts/lib/ptxd_make_get.sh)... but I don't quite understand how > > to integrate this in my rules/*.make file. > > 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 :) > However I'm also curious about other ways. Is there a nice ptxdist way > to handle packages without tarball coming directly from some git repo? > > Greets > Alex > > > > -- > ptxdist mailing list > ptxdist@pengutronix.de > > --001a11c281088ec6f904ef6f5fb3 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On W= ed, Jan 8, 2014 at 12:56 AM, Alexander Dahl <post@lespocky.de> wrote:
Hei hei,

On 08.01.2014 03:32, Jon Ringle wrote:
> My initial thought is to create a git repo that holds the ptxconfig fi= les
> and local rules/, and then configure the rules to somehow get the git = repos
> by tag for building (as it seems that there is some sort of support fo= r
> this in scripts/lib/ptxd_make_get.sh)... but I don't quite underst= and how
> to integrate this in my rules/*.make file.

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<= br> interested in the scripts, tell me.


Yes, I would be interested to see your scripts an= d how you use them in your *.make and *.in :)
=A0
However I'm also curious about other ways. Is there a nice ptxdist way<= br> to handle packages without tarball coming directly from some git repo?

Greets
Alex



--
ptxdist mailing list
ptxdist@pengutronix.de


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