[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Cleanup initialization of configure process (issue 549350043 by addr

From: jonas . hahnfeld
Subject: Re: Cleanup initialization of configure process (issue 549350043 by address@hidden)
Date: Wed, 08 Jan 2020 09:48:36 -0800

On 2020/01/08 16:43:24, dak wrote:
mailto:address@hidden writes:

> Reviewers: dak,
> Message:
> On 2020/01/08 16:18:25, dak wrote:
>> File (right):
>> AC_INIT([LilyPond], [2.21.0],
>> [lilypond], [])
>> Hardwiring the version number in this manner is a real maintenance
>> Couldn't create a VERSION.AC file (or something like it)
>> only the version number that is just included here?
> I agree that it's essentially duplicated, but it's not that we bump
> version every day. To make sure there's no divergence, I added a
> that the one provided in AC_INIT and in VERSION are the same.
> Ideally, I'd like to get rid of the VERSION completely, but
> you can build the website without configure'ing the project. I
> sure if that is still used, so I went for this solution.

That doesn't answer my question, does it?

Maybe I mis-understood your suggestion: I thought you're asking if
configure can create a file that can be used in place of the current
version. That doesn't work because "make website" can be called without
configure'ing (not sure if that is used, it's certainly different from
how other projects using the GNU build system works)

But re-reading your question, you're maybe proposing to have a file that
is included by Autoconf when generating configure? I think that's not
possible with the documented functionality of Autoconf because you can
only do very few things before calling AC_INIT. I've not come across
something that can read a file in that situation.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]