Re: How to build libtool from git sources properly?

[Pavel Raiskup]

On Thursday, May 19, 2016 8:56:20 AM CEST Bruce Korb wrote:
> On Thu, May 19, 2016 at 7:22 AM, Eric Blake  wrote:
> > ... However, libtool uses its own
> > custom bootstrap, and I don't know if it has that same functionality.
> > Patches are certainly welcome.  And it would also be nice if libtool's
> > own bootstrap could be merged back upstream with gnulib's bootstrap.
> 
> I believe the author of the script wanted to do just that, but felt he
> had headwinds.
> Now, it's too late as he can't do open source development anymore.
> (Employer requirements.)  I use the libtool bootstrap for a couple of my
> projects and I, too, think it would be good to merge it back into gnulib.

This is/was my personal long-term task, too.

Gary has trying to merge this into gnulib for a long time;  and it is not
going to be much easier now so, to not C everything all the time, we
agreed with Gary that we'll have the bootstrap project at least
"pluggable" into gnulib for now.

>From our last discussion, merging those two bootstraps together into
gnulib HEAD (and retiring boostrap) is something which is desired.  On the
other hand, for the time being, we can benefit from the fact that Gary can
have a look at isolated bootstrap code.

> I have no employer requirements anymore, but I have my own projects on
> the table, so gnulib patch delivery time might get measured in weeks.

In case you'll have a chance to look at this, keep us updated :) !

Pavel


___
https://lists.gnu.org/mailman/listinfo/libtool

Re: How to build libtool from git sources properly?

[Bruce Korb]

On Thu, May 19, 2016 at 7:22 AM, Eric Blake  wrote:
> ... However, libtool uses its own
> custom bootstrap, and I don't know if it has that same functionality.
> Patches are certainly welcome.  And it would also be nice if libtool's
> own bootstrap could be merged back upstream with gnulib's bootstrap.

I believe the author of the script wanted to do just that, but felt he
had headwinds.
Now, it's too late as he can't do open source development anymore.
(Employer requirements.)  I use the libtool bootstrap for a couple of my
projects and I, too, think it would be good to merge it back into gnulib.
I have no employer requirements anymore, but I have my own projects
on the table, so gnulib patch delivery time might get measured in weeks.

___
https://lists.gnu.org/mailman/listinfo/libtool

Re: How to build libtool from git sources properly?

[Eric Blake]

On 05/19/2016 12:56 AM, Igor Zhbanov wrote:
> 
> 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.

Projects that use gnulib's bootstrap can set environment variables to
point to a local clone of gnulib.git.  However, libtool uses its own
custom bootstrap, and I don't know if it has that same functionality.
Patches are certainly welcome.  And it would also be nice if libtool's
own bootstrap could be merged back upstream with gnulib's bootstrap.

-- 
Eric Blake   eblake redhat com+1-919-301-3266
Libvirt virtualization library http://libvirt.org



signature.asc
Description: OpenPGP digital signature
___
https://lists.gnu.org/mailman/listinfo/libtool

Re: How to build libtool from git sources properly?

[Igor Zhbanov]

19 мая 2016 г. 3:57 пользователь "Bruce Korb" 
написал:
>
> 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.
___
https://lists.gnu.org/mailman/listinfo/libtool

Re: How to build libtool from git sources properly?

[Mathieu Lirzin]

Hi,

Bob Friesenhahn  writes:

> 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.

Why?  Development repositories are not meant for end users.  Having a
tarball requiring only a subset of the dependencies necessary or
convenient to the developers seems nice.

> 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.
>
> The bootstrap requirements make it difficult to support or test on
> targets which can not run git or don't have network access.

To test a unreleased version of a package that uses the GNU build system
on a restricted system, the usual method would be to bootstrap a tarball
with ‘make dist’ from a development machine with Git, network access,
... and then install the produced tarball on the targeted machine.

-- 
Mathieu Lirzin

___
https://lists.gnu.org/mailman/listinfo/libtool

Re: How to build libtool from git sources properly?

[Bruce Korb]

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".

___
https://lists.gnu.org/mailman/listinfo/libtool

Re: How to build libtool from git sources properly?

[Bob Friesenhahn]

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.


The bootstrap requirements make it difficult to support or test on 
targets which can not run git or don't have network access.


Bob
--
Bob Friesenhahn
bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,http://www.GraphicsMagick.org/

___
https://lists.gnu.org/mailman/listinfo/libtool

Re: How to build libtool from git sources properly?

[Igor Zhbanov]

Hi Mike,

2016-05-18 16:57 GMT+03:00 Mike Frysinger <vap...@gentoo.org>:
> On 18 May 2016 11:15, Igor Zhbanov wrote:
>> How to properly build libtool from git sources.
>>
>> I see too many differences between
>>
>> git clone git://git.savannah.gnu.org/libtool.git
>> git checkout v2.4.6
>>
>> and
>>
>> http://ftpmirror.gnu.org/libtool/libtool-2.4.6.tar.gz.
>>
>> How to make cloned sources to look like in release archive?
>> Didn't find any instruction.
>
> 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.

Thanks.

___
https://lists.gnu.org/mailman/listinfo/libtool

Re: How to build libtool from git sources properly?

[Mike Frysinger]

On 18 May 2016 11:15, Igor Zhbanov wrote:
> How to properly build libtool from git sources.
> 
> I see too many differences between
> 
> git clone git://git.savannah.gnu.org/libtool.git
> git checkout v2.4.6
> 
> and
> 
> http://ftpmirror.gnu.org/libtool/libtool-2.4.6.tar.gz.
> 
> How to make cloned sources to look like in release archive?
> Didn't find any instruction.

run `./bootstrap`
-mike


signature.asc
Description: Digital signature
___
https://lists.gnu.org/mailman/listinfo/libtool

How to build libtool from git sources properly?

[Igor Zhbanov]

Hi!

How to properly build libtool from git sources.

I see too many differences between

git clone git://git.savannah.gnu.org/libtool.git
git checkout v2.4.6

and

http://ftpmirror.gnu.org/libtool/libtool-2.4.6.tar.gz.

How to make cloned sources to look like in release archive?
Didn't find any instruction.

Thank you.

___
https://lists.gnu.org/mailman/listinfo/libtool