Hello. I propose to add to bootstrap key --skip-git (analog --skip-po), completely eliminates the use git in the bootstrap process. Now this behavior may occur if the directory specified by --gnulib-srcdir (or specified in the $ GNULIB_SRCDIR) not git repository. But it is desirable to have the option disables the use git explicitly (see <https://bugzilla.redhat.com/show_bug.cgi?id=562743#c27>).
As the implementation of the proposed <http://git.altlinux.org/people/solo/public/gnulib.git?p=gnulib.git;a=commit;h=162e7f34257f4f213d4db54d6e82d809be2d2061>. This further development of patch adds the option - no-git (see <http://lists.gnu.org/archive/html/bug-gnulib/2010-03/msg00229.html>), combined with a fresh bootstrap and some simplified. A brief explanation of why this is necessary (in the context of building libvirt, quoting <https://bugzilla.redhat.com/show_bug.cgi?id=562743#c19>): 1. I build the package is not from the official tarball, but directly from the git repository transferred to the build system. All the necessary tarballs, sent directly to the assembly, build system creates itself, from these I commit. 2. Accessing external resources in the process of assembly (and / or at the preparatory stage tarballs build system), we considered a serious bug: all downloads must be fulfilled by man (in preparation for repository transferred to the assembly) and not a robot. Such is the policy of our distribution. 2. In any case, I want to replace files autotool (autoconf, automake, libtool, etc.) distributive -- are with us are often patched. By virtue of paragraph 1 (source git and not the official tarball) in any case, I want to form the desired gnulib (=> run the bootstrap). It is logical to assign this work the robot (build system). Robot (build system) has no right to do git submodule update (Clause 2), but can generate tarball from a given commit and deploy it in the specified directory. If you transfer this directory through $ GNULIB_SRCDIR bootstrap works off without causing a git. (With me and you want: no need to put in git to build chroot.) If $GNULIB_SRCDIR used during assembly does not contain the right - build fails, you may need to correct his hands: build system should not perform such things as a git submodule update in Clause 2. Common sense patches bootstrap.conf - an exception to that requirement in the given conditions bootstrap does not actually use: git is not necessary when you specify $GNULIB_SRCDIR, but rsync is not necessary if you set $SKIP_PO. (If the original bootstrap.conf git and rsync always required.) I do not see that these patches can break. Important for me as functional, they add. -- Yours. Aleksey.
signature.asc
Description: OpenPGP digital signature
