Dear all,
I am trying to define a package version properly by first defining its
components separately (major and minor version number, patchlevel, and
extra).
The major and minor numbers are assumed to be always present. The
patchlevel and the extra bits are optional.
In pseudo-shell code, the
On 2021-08-23, Sébastien Hinderer wrote:
> I would like to express all this in m4, more precisely in aclocal.m4, so
> that the configure script has proper version information.
>
> At the moment I don't manage to do so and failed to find an exemple of a
> macro whose body can take several lines but
On 2021-08-23, Nick Bowler wrote:
> However, you might not notice that this text went unexpanded in
> Autoconf (which is in effect while processing aclocal.m4) is KILL,
> so all resulting text is simply discarded.
Erm, I appear to have accidentally some words...
I meant to say "the default diver
Hi Sebastien,
On 24/8/21 2:49 am, Sébastien Hinderer wrote:
Dear all,
I am trying to define a package version properly by first defining its
components separately (major and minor version number, patchlevel, and
extra).
The major and minor numbers are assumed to be always present. The
patchlev
