Re: Moving away from autoconf

2016-02-24 Thread Aaron Klotz

Giggity

On 2/24/2016 3:28 PM, Mike Hommey wrote:

Hi,

We are, officially, and starting today with the landing of bug 1250294,
moving away from autoconf. This is not going to happen overnight, and it
is going to be painful, but the first step has just been made, and we're
not turning back.

The autoconf scripts are however still there and are used, but were
renamed to old-configure.in. If you have pending patches against
configure.in or js/src/configure.in, your changes will need to be
applied to old-configure.in or js/src/old-configure.in.

Cheers,

Mike
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Re: Moving away from autoconf

2016-02-24 Thread Mike Hommey
On Wed, Feb 24, 2016 at 03:38:35PM -0800, Ralph Giles wrote:
> Where do new changes go?

The answer to this question will change in the coming days, and vary
depending on what you want to change. Please ask build system peers.
I should have mentioned this in the original message, sorry.

Mike
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Re: Moving away from autoconf

2016-02-24 Thread Tom Schuster
This is so great. Thank you!
On Feb 25, 2016 12:35 AM, "Mike Hommey"  wrote:

> Hi,
>
> We are, officially, and starting today with the landing of bug 1250294,
> moving away from autoconf. This is not going to happen overnight, and it
> is going to be painful, but the first step has just been made, and we're
> not turning back.
>
> The autoconf scripts are however still there and are used, but were
> renamed to old-configure.in. If you have pending patches against
> configure.in or js/src/configure.in, your changes will need to be
> applied to old-configure.in or js/src/old-configure.in.
>
> Cheers,
>
> Mike
> ___
> dev-platform mailing list
> dev-platform@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-platform
>
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Re: Moving away from autoconf

2016-02-24 Thread Ralph Giles
Where do new changes go?

 -r

On Wed, Feb 24, 2016 at 2:28 PM, Mike Hommey  wrote:
> Hi,
>
> We are, officially, and starting today with the landing of bug 1250294,
> moving away from autoconf. This is not going to happen overnight, and it
> is going to be painful, but the first step has just been made, and we're
> not turning back.
>
> The autoconf scripts are however still there and are used, but were
> renamed to old-configure.in. If you have pending patches against
> configure.in or js/src/configure.in, your changes will need to be
> applied to old-configure.in or js/src/old-configure.in.
>
> Cheers,
>
> Mike
> ___
> dev-platform mailing list
> dev-platform@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-platform
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Moving away from autoconf

2016-02-24 Thread Mike Hommey
Hi,

We are, officially, and starting today with the landing of bug 1250294,
moving away from autoconf. This is not going to happen overnight, and it
is going to be painful, but the first step has just been made, and we're
not turning back.

The autoconf scripts are however still there and are used, but were
renamed to old-configure.in. If you have pending patches against
configure.in or js/src/configure.in, your changes will need to be
applied to old-configure.in or js/src/old-configure.in.

Cheers,

Mike
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform