Re: [ptxdist] git ptxdist best practices

["Olbrich, Michael" <m.olbrich@pengutronix.de>]

On Wed, Jan 08, 2014 at 08:59:43AM +0100, Jürgen Beisert wrote:
> 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.

It really depends on how you want to work with this. If the external
repositories are integrated often, then add them as git submodules in
local_src and use "file://$(PTXDIST_WORKSPACE)/local_src/foo/" as URL. If
not then create a tag when integrating and use
git://myhost.de/foo.git;tag=mytag1" as URL and foo-mytag1.tar.bz2 as SOURCE
and update the tag as needed.  This will clone the repository and create a
tarball for the tag. Note: you cannot follow a branch here! It will just
use the tarball and ignore any changes to the branch. This is only for
projects that only provide git tags for releases but no tarballs.

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