mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: "Jürgen Beisert" <jbe@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] git ptxdist best practices
Date: Wed, 8 Jan 2014 10:52:17 +0100	[thread overview]
Message-ID: <201401081052.17919.jbe@pengutronix.de> (raw)
In-Reply-To: <7b9f505c08f5635b7ea7dd90cc41ce89@idefix.lespocky.dyndns.org>

On Wednesday 08 January 2014 10:21:53 Alexander Dahl wrote:
> 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 "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.

<nothing>

More coffee? :))

jbe

-- 
Pengutronix e.K.                              | Juergen Beisert             |
Linux Solutions for Science and Industry      | http://www.pengutronix.de/  |

-- 
ptxdist mailing list
ptxdist@pengutronix.de

  parent reply	other threads:[~2014-01-08  9:52 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-08  2:32 Jon Ringle
2014-01-08  5:56 ` Alexander Dahl
2014-01-08  6:12   ` Jon Ringle
2014-01-08  9:21     ` Alexander Dahl
2014-01-08  9:48       ` Alexander Dahl
2014-01-08  9:52       ` Jürgen Beisert [this message]
2014-01-08 17:56       ` Jon Ringle
2014-01-08 20:43         ` Alexander Dahl
2014-01-08  7:59 ` Jürgen Beisert
2014-01-08 14:14   ` Jon Ringle
2014-01-09  8:10     ` Jürgen Beisert
2014-01-09  9:03   ` Olbrich, Michael
2014-01-09 15:23     ` Jon Ringle
2014-01-09 16:06       ` Michael Olbrich
2014-01-09 16:37         ` Jon Ringle
2014-01-10 15:37           ` Michael Olbrich
2014-01-10 15:41             ` Jon Ringle
2014-01-11  1:47             ` Jon Ringle
2014-01-24  9:21               ` Michael Olbrich
2014-01-24 13:10                 ` Jon Ringle

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=201401081052.17919.jbe@pengutronix.de \
    --to=jbe@pengutronix.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