From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail-la0-x230.google.com ([2a00:1450:4010:c03::230]) by metis.ext.pengutronix.de with esmtp (Exim 4.72) (envelope-from ) id 1W1HSm-0004Uh-UR for ptxdist@pengutronix.de; Thu, 09 Jan 2014 16:24:08 +0100 Received: by mail-la0-f48.google.com with SMTP id n7so2252165lam.7 for ; Thu, 09 Jan 2014 07:23:59 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <20140109090334.GI2156@pengutronix.de> References: <201401080859.43988.jbe@pengutronix.de> <20140109090334.GI2156@pengutronix.de> Date: Thu, 9 Jan 2014 10:23:58 -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="===============0495607912==" Sender: ptxdist-bounces@pengutronix.de Errors-To: ptxdist-bounces@pengutronix.de To: ptxdist@pengutronix.de --===============0495607912== Content-Type: multipart/alternative; boundary=001a11c38892d14c6904ef8b324c --001a11c38892d14c6904ef8b324c Content-Type: text/plain; charset=ISO-8859-1 On Thu, Jan 9, 2014 at 4:03 AM, Olbrich, Michael wrote: > 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 > I've not used git submodules before. Can I bind a git submodule to a specific tag? > 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. > > One issue that I ran across with this is that I have: PTXCONF_SETUP_PTXMIRROR_ONLY=y PTXCONF_SETUP_PTXMIRROR="http://opensource/pool/" Where opensource is an internal server that keeps all tar balls used to build. I'm paranoid that someday a upstream tar ball won't be available and would cause a build break if someone tried to build and they didn't have that tar ball in ${PTXCONF_SETUP_SRCDIR} But for my purposes, if I wanted to use the git URL in a rule file I'd want it to use the URL as is. But it rewrites it trying to use ${PTXCONF_SETUP_PTXMIRROR} instead in scripts/lib/ptxd_make_get.sh:295 Is there away to work around this? --001a11c38892d14c6904ef8b324c Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On T= hu, Jan 9, 2014 at 4:03 AM, Olbrich, Michael <m.olbrich@pengutroni= x.de> wrote:
It really depends on how you want to work with this. If the ext= ernal
repositories are integrated often, then add them as git submodules in
local_src and use "file://$(PTXDIST_WORKSPACE)/local_src/foo/" as= URL. If

I've not used git submodules before. C= an I bind a git submodule to a specific tag?
=A0
not then create a tag when integrating and use
git://m= yhost.de/foo.git;tag=3Dmytag1" as URL and foo-mytag1.tar.bz2 as SO= URCE
and update the tag as needed. =A0This 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.


One issue that I ran across with this is that I have:
PTXCONF_SETU= P_PTXMIRROR_ONLY=3Dy
PTXCONF_SETUP_PTXMIRROR=3D"http://opensource/pool/"

Where opensource is an internal server that keeps all tar ba= lls used to build. I'm paranoid that someday a upstream tar ball won= 9;t be available and would cause a build break if someone tried to build an= d they didn't have that tar ball in ${PTXCONF_SETUP_SRCDIR}

But for my purposes, if I wanted to use the git URL in a rul= e file I'd want it to use the URL as is. But it rewrites it trying to u= se ${PTXCONF_SETUP_PTXMIRROR} instead in scripts/lib/ptxd_make_get.sh:295
Is there away to work around this?


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