From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from moutng.kundenserver.de ([212.227.17.9]) by metis.ext.pengutronix.de with esmtp (Exim 4.72) (envelope-from ) id 1W0m8g-0002VE-49 for ptxdist@pengutronix.de; Wed, 08 Jan 2014 06:57:34 +0100 Received: from buffy.lespocky.dyndns.org ([10.182.63.86]) by idefix.lespocky.dyndns.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.80.1) (envelope-from ) id 1W0m8U-0000P9-B4 for ptxdist@pengutronix.de; Wed, 08 Jan 2014 06:57:07 +0100 Message-ID: <52CCE8A8.8070906@lespocky.de> Date: Wed, 08 Jan 2014 06:56:56 +0100 From: Alexander Dahl MIME-Version: 1.0 References: In-Reply-To: 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="===============2088749621==" Sender: ptxdist-bounces@pengutronix.de Errors-To: ptxdist-bounces@pengutronix.de To: ptxdist@pengutronix.de This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --===============2088749621== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="----enig2KNFTRCTBBGQMBJLOWPSK" This is an OpenPGP/MIME signed message (RFC 4880 and 3156) ------enig2KNFTRCTBBGQMBJLOWPSK Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hei hei, On 08.01.2014 03:32, Jon Ringle wrote: > My initial thought is to create a git repo that holds the ptxconfig fil= es > and local rules/, and then configure the rules to somehow get the git r= epos > 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 h= ow > 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. 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 ------enig2KNFTRCTBBGQMBJLOWPSK Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iEYEARECAAYFAlLM6K4ACgkQj7p3RMyHENDCGQCgxhBksPA5ob7GLh5TU4F8FKxQ mr4AnRP1xr1+mzu6LVA2asRMCk34Vxxf =BZt+ -----END PGP SIGNATURE----- ------enig2KNFTRCTBBGQMBJLOWPSK-- --===============2088749621== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline -- ptxdist mailing list ptxdist@pengutronix.de --===============2088749621==--