From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Message-ID: <4B4994C1.7060406@altlinux.com> Date: Sun, 10 Jan 2010 11:50:09 +0300 From: Anton Farygin User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.5pre) Gecko/20091019 Thunderbird/3.0pre MIME-Version: 1.0 To: ALT Linux Team development discussions References: <20100109224328.GB14247@wo.int.altlinux.org> In-Reply-To: <20100109224328.GB14247@wo.int.altlinux.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit 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 List-Id: ALT Linux Team development discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Jan 2010 08:50:20 -0000 Archived-At: List-Archive: List-Post: 10.01.2010 01:43, Dmitry V. Levin пишет: > 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. Это хороший метод, но он зачастую неудобен - git репозиторий вырастает до непотребных размеров (700Mb, для примера), получающийся из суммы всех submodules. git fetch --depth помог бы, но такие репозитории у меня не получилось выложить на git.alt.