On Wed, 23 Apr 2008, Eric Blake wrote:
> I'm not quite sure what is best to do here. It seems like the simplest
> wrapper might be this untested script (short enough to possibly be worth
> distributing without copyright notice, since adding the notice would
> double its size):
>
> #!/bin/sh
> if
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Jim Meyering on 4/23/2008 4:28 AM:
| I was going to suggest this:
|
| Send a properly git-attributed patch (i.e., trivial for me to
| apply with "git am your-patch" -- see coreutils' HACKING for details)
| and I'll apply it.
|
| but
On Wed, 23 Apr 2008, Jim Meyering wrote:
> > I was hoping for something more formal: all developers commit their
> > bootstrap-inner.m4sh changes to gnulib instead of to their own projects.
>
> That's already the idea, using gnulib's bootstrap.
Ok, thanks. I wasn't aware.
> > Writing bootstrap
"Joel E. Denny" <[EMAIL PROTECTED]> wrote:
> On Wed, 23 Apr 2008, Jim Meyering wrote:
>
>> > I was hoping for something more formal: all developers commit their
>> > bootstrap-inner.m4sh changes to gnulib instead of to their own projects.
>>
>> That's already the idea, using gnulib's bootstrap.
>
"Joel E. Denny" <[EMAIL PROTECTED]> wrote:
> On Tue, 22 Apr 2008, Jim Meyering wrote:
>
>> "Joel E. Denny" <[EMAIL PROTECTED]> wrote:
>
>> There's already a bootstrap module in gnulib.
>
> You mean build-aux/bootstrap?
Yes.
>> We sync things around periodically.
>
> I was hoping for something mor
On Tue, 22 Apr 2008, Jim Meyering wrote:
> "Joel E. Denny" <[EMAIL PROTECTED]> wrote:
> There's already a bootstrap module in gnulib.
You mean build-aux/bootstrap?
> We sync things around periodically.
I was hoping for something more formal: all developers commit their
bootstrap-inner.m4sh ch
On Tue, 22 Apr 2008, Jim Meyering wrote:
> > as the preferred method for getting started, avoiding the need to check in
> > bootstrap? Or even have a two-level bootstrap: ./bootstrap is a simple
> > checked-in wrapper which portably calls autom4te on bootstrap_inner.m4sh
> > then runs bootstrap_i
"Joel E. Denny" <[EMAIL PROTECTED]> wrote:
> On Tue, 22 Apr 2008, Jim Meyering wrote:
>
>> > as the preferred method for getting started, avoiding the need to check in
>> > bootstrap? Or even have a two-level bootstrap: ./bootstrap is a simple
>> > checked-in wrapper which portably calls autom4te
Eric Blake <[EMAIL PROTECTED]> wrote:
> According to Jim Meyering on 4/22/2008 7:23 AM:
> |> Is it worth writing bootstrap.m4sh, and running it through autom4te to get
> |> the shell selection code from autoconf with minimal effort on your part?
> |> You'd still probably want to check in the gener
Eric Blake <[EMAIL PROTECTED]> wrote:
> According to Jim Meyering on 4/22/2008 3:42 AM:
> | I'll probably change the instructions in README-hacking to mention
> | that you may have to run "bash ./bootstrap" rather than
> |
> | $ ./bootstrap
> |
> | if your system's /bin/sh is substandard.
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Jim Meyering on 4/22/2008 3:42 AM:
| I'll probably change the instructions in README-hacking to mention
| that you may have to run "bash ./bootstrap" rather than
|
| $ ./bootstrap
|
| if your system's /bin/sh is substandard.
Sounds
"Joel E. Denny" <[EMAIL PROTECTED]> wrote:
> Coreutils maintainers,
>
> It appears that Bison's bootstrap script is occasionally sync'ed against
> Coreutils'. Paul Hilfinger, one of the Bison developers, recently made
> the discovery quoted below, which I figure might also be relevant to
> Coreuti
Coreutils maintainers,
It appears that Bison's bootstrap script is occasionally sync'ed against
Coreutils'. Paul Hilfinger, one of the Bison developers, recently made
the discovery quoted below, which I figure might also be relevant to
Coreutils.
On Fri, 4 Apr 2008, Joel E. Denny wrote:
> On
13 matches
Mail list logo
