mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: "Jürgen Beisert" <jbe@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: "Olbrich, Michael" <m.olbrich@pengutronix.de>
Subject: Re: [ptxdist] git ptxdist best practices
Date: Wed, 8 Jan 2014 08:59:43 +0100	[thread overview]
Message-ID: <201401080859.43988.jbe@pengutronix.de> (raw)
In-Reply-To: <CAMwGMjx4iu-2w2OVEpjX7T9USnzEAE70XH+pff_ksaCuvA63Wg@mail.gmail.com>

Hi Jon,

On Wednesday 08 January 2014 03:32:41 Jon Ringle wrote:
> I'm looking for some best practices ideas as it relates to using ptxdist to
> build a complete system that pulls from various git repos.
>
> I have a clone Linux git repo that has local commits specific to our
> embedded hardware.
> I build an initramfs filesystem with ptxdist that gets embedded within the
> Linux kernel image.
> I build a rootfs with ptxdist for the real rootfs
> I also have a couple of libs and apps that have their own git repos as well
> that I'm getting ptxdist to build as well.
>
> I'm now at the point where I now need to make this available to other
> developers and also get setup for a build bot to build (bamboo).
>
> 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.
>
> Perhaps there is a better way of doing this. I'd be interested to hear what
> others are doing in this regard.

Do you want to use this BSP only by your own, or is it intended to provide it 
to other developers who use it as a base for their own work?

In the latter case I would "release" the various components and create archives 
of it. And these archives can simply be part of the (finally) released BSP you 
provide to other developers (in contrast to the downloadable archives PTXdist 
uses for the remaining packages like Busybox, Qt and so on).

If you still want to use git repositories for the external components we should 
wait for Michael, because he can explain how to use the PTXdist feature which 
deals with such repositories.

Regards,
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  7:59 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
2014-01-08 17:56       ` Jon Ringle
2014-01-08 20:43         ` Alexander Dahl
2014-01-08  7:59 ` Jürgen Beisert [this message]
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=201401080859.43988.jbe@pengutronix.de \
    --to=jbe@pengutronix.de \
    --cc=m.olbrich@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