Re: How to build libtool from git sources properly?

[Igor Zhbanov]

19 мая 2016 г. 3:57 пользователь "Bruce Korb" <address@hidden> написал:
>
> On 05/18/16 14:41, Bob Friesenhahn wrote:
>>
>> On Wed, 18 May 2016, Igor Zhbanov wrote:
>>>>
>>>>
>>>> run `./bootstrap`
>>>> -mike
>>>
>>>
>>> It doesn't work on a PC without git or without network connection
>>> because it needs to clone gnulib (although there is no gnulib folder
>>> in libtool-2.4.6.tar.gz. But this is probably another story.
>>
>>
>> This is very unfortunate.  I am not sure if it would work if you cloned
>> gnulib on another computer and copied the gnulib folder into place since
>> it may still make subsequent git accesses.
>
>
> It sounds to me like Igor wants/needs the release tarball.
> Pulling from GIT and building is a maintainer problem.
> If you are going to help maintain it, you need access to
> maintainer stuff:  GIT, gnulib, the internet, etc.
> It's "by design".

I wanted to build it from a local git mirror (a protection against network outages on our or your side), checking out on v2.4.6 tag. So when a new release would be available, I would simply change the commit hash in a local git submodule. But I've found that it's not enough to have sources of libtool because it needs sources of gnulib. And it's impossible to build it from unmodified sources if you want to build it without network access, because you need at least patch it to use local version of gnulib.

So I moved to build it from release tarballs. Although almost all other packages are build from locall git mirrors.

P.S. Few days ago there were problems with Savannah hosting, so you can't even clone GNU projects. So this scenario is not hypothetical, that's why having local git mirrors is a must if you want to build packages at any time.