Hi Simon,
On 11 Jan 2012, at 21:51, Simon Josefsson wrote:
> Could you point me towards some project that uses the latest
> version of your script?
Sure!
Peek at the code here:
http://git.savannah.gnu.org/cgit/zile.git/tree/
Clone the repo like this:
$ git clone git://git.savannah.gnu.org
Hi Simon,
On 11 Jan 2012, at 22:08, Simon Josefsson wrote:
> "Gary V. Vaughan" writes:
>> Now that I think about it, I'd like to put the multi-gnulib support
>> directly into my bootstrap script so that it can be called by setting
>> some configuration variables in bootstrap.conf rather than prol
"Gary V. Vaughan" writes:
> Now that I think about it, I'd like to put the multi-gnulib support
> directly into my bootstrap script so that it can be called by setting
> some configuration variables in bootstrap.conf rather than proliferating
> a hook function among all the projects that need thi
Hi Simon,
On 11 Jan 2012, at 21:35, Gary V. Vaughan wrote:
> On 11 Jan 2012, at 20:57, Simon Josefsson wrote:
>> [[...]] for some reason, my projects
>> often follow a pattern where they need to have multiple gnulib
>> instances.
>
> [[...]] I think this setup is a fairly common requirement
> for
"Gary V. Vaughan" writes:
> Hi Simon,
>
> On 11 Jan 2012, at 20:57, Simon Josefsson wrote:
>> [[...]] for some reason, my projects
>> often follow a pattern where they need to have multiple gnulib
>> instances. Last time I looked, bootstrap couldn't handle this, can
>> yours?
>
> Yes it can.
>
>
Hi Simon,
On 11 Jan 2012, at 20:57, Simon Josefsson wrote:
> [[...]] for some reason, my projects
> often follow a pattern where they need to have multiple gnulib
> instances. Last time I looked, bootstrap couldn't handle this, can
> yours?
Yes it can.
Actually another part of the (many) reason
"Gary V. Vaughan" writes:
>> I haven't tried yet but a quick look into the code seems to confirm
>> that Gary's `bootstrap' file can do that. In case this is true I
>> really recommend to use his version as the default in gnulib.
>
> I agree with this too :)
>
> However, I understand that review
On 11 Jan 2012, at 12:59, Werner LEMBERG wrote:
>> Since then, I've broken out some functionality into reusable
>> standalone scripts that will be useful for replacing the hairy
>> sed-and-grep method of interrogating the m4 macros used by
>> configure.ac with a much more robust and faster call to
> Since then, I've broken out some functionality into reusable
> standalone scripts that will be useful for replacing the hairy
> sed-and-grep method of interrogating the m4 macros used by
> configure.ac with a much more robust and faster call to parse the m4
> macros with GNU M4!
Parsing m4 macro
Hi Werner,
On 11 Jan 2012, at 12:30, Werner LEMBERG wrote:
After doing the incantation described in section 2.8 of gnulib.pdf,
namely
$ dir=.gnulib
$ git submodule add -- git://git.sv.gnu.org/gnulib.git $dir
the user has to commit the submodule setup to the r
>>> After doing the incantation described in section 2.8 of gnulib.pdf,
>>> namely
>>>
>>> $ dir=.gnulib
>>> $ git submodule add -- git://git.sv.gnu.org/gnulib.git $dir
>>>
>>> the user has to commit the submodule setup to the repository. It's
>>> probably worth to mention this.
>>>
>>> Howev
On 01/10/2012 12:30 PM, Werner LEMBERG wrote:
>
>> After doing the incantation described in section 2.8 of gnulib.pdf,
>> namely
>>
>> $ dir=.gnulib
>> $ git submodule add -- git://git.sv.gnu.org/gnulib.git $dir
>>
>> the user has to commit the submodule setup to the repository. It's
>> proba
> Perhaps you could try my rewrite of the bootstrap script, with which
> I cannot reproduce the problem you describe?
Will do that eventually, thanks.
> I'm unsure how to proceed. On one hand, I like `.gnulib' as the
> submodule's directory. On the other hand, I don't like `.gnulib' as
> the s
> After doing the incantation described in section 2.8 of gnulib.pdf,
> namely
>
> $ dir=.gnulib
> $ git submodule add -- git://git.sv.gnu.org/gnulib.git $dir
>
> the user has to commit the submodule setup to the repository. It's
> probably worth to mention this.
>
> However, if I now say
Hi Werner,
On 11 Jan 2012, at 01:40, Werner LEMBERG wrote:
>>> . First of all, there is some user-unfriendliness: Without
>>> installing a gnulib submodule for project `foo', just invoking
>>> the `bootstrap' script in the `foo' directory' without any
>>> arguments gives
>>>
>>>./bootstrap
>> . First of all, there is some user-unfriendliness: Without
>> installing a gnulib submodule for project `foo', just invoking
>> the `bootstrap' script in the `foo' directory' without any
>> arguments gives
>>
>> ./bootstrap: line 610: gnulib/gnulib-tool: No such file or directory
>>
On 01/10/2012 08:20 AM, Werner LEMBERG wrote:
>
> [gnulib 530dd174]
>
>
> The `git submodule' is a very nice feature, however, there are two
> issues.
>
> . First of all, there is some user-unfriendliness: Without
> installing a gnulib submodule for project `foo', just invoking the
>
[gnulib 530dd174]
The `git submodule' is a very nice feature, however, there are two
issues.
. First of all, there is some user-unfriendliness: Without
installing a gnulib submodule for project `foo', just invoking the
`bootstrap' script in the `foo' directory' without any arguments
18 matches
Mail list logo
