From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <ldv@altlinux.org>
Date: Sun, 10 Jan 2010 01:43:28 +0300
From: "Dmitry V. Levin" <ldv@altlinux.org>
To: ALT Linux Team development discussions <devel@lists.altlinux.org>
Message-ID: <20100109224328.GB14247@wo.int.altlinux.org>
Mail-Followup-To: ALT Linux Team development discussions
	<devel@lists.altlinux.org>
References: <fbfa7b0c1001091219vf91232eke112b8952139c44@mail.gmail.com>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="jq0ap7NbKX2Kqbes"
Content-Disposition: inline
In-Reply-To: <fbfa7b0c1001091219vf91232eke112b8952139c44@mail.gmail.com>
X-fingerprint: FE4C 93AB E19A 2E4C CB5D  3E4E 7CAB E6AC 9E35 361E
Subject: Re: [devel] git submodules on git.alt
X-BeenThere: devel@lists.altlinux.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: ALT Linux Team development discussions <devel@lists.altlinux.org>
List-Id: ALT Linux Team development discussions <devel.lists.altlinux.org>
List-Unsubscribe: <https://lists.altlinux.org/mailman/options/devel>,
	<mailto:devel-request@lists.altlinux.org?subject=unsubscribe>
List-Archive: <http://lists.altlinux.org/pipermail/devel>
List-Post: <mailto:devel@lists.altlinux.org>
List-Help: <mailto:devel-request@lists.altlinux.org?subject=help>
List-Subscribe: <https://lists.altlinux.org/mailman/listinfo/devel>,
	<mailto:devel-request@lists.altlinux.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Jan 2010 22:43:29 -0000
Archived-At: <http://lore.altlinux.org/devel/20100109224328.GB14247@wo.int.altlinux.org/>
List-Archive: <http://lore.altlinux.org/devel/>
List-Post: <mailto:devel@altlinux.org>


--jq0ap7NbKX2Kqbes
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sat, Jan 09, 2010 at 08:19:09PM +0000, Max Ivanov wrote:
> How to deal with git submodules? Upstream uses them in some places and
> I don't know how to put their content in the final source tree prior
> to %build stage. Is it even possible?

Due to the fundamental problem already described in this thread, you
cannot use git submodules AS IS to build packages using gear.  There is
simple workaround you can use to overcome this problem:
1. Extract each submodule into separate tarball using appropriate
   .gear/rules; this is trivial because you know commit ids.
2. Make sure that your build commit inherits to all these submodule
   commits.

Unfortunately, there are no means in gear-update-*whatever* yet to
automate this work.


--=20
ldv

--jq0ap7NbKX2Kqbes
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAktJBpAACgkQfKvmrJ41Nh5DfQCgsvzqJJ1BF5ot9aP56oPwca4O
Bo4An0xROhb+4Lp2AzwhFLP2i0MNgzkL
=UIR4
-----END PGP SIGNATURE-----

--jq0ap7NbKX2Kqbes--