On Sun, Jan 28, 2024 at 08:49:36PM +, Gavin Smith wrote:
>
> I like get_build_constant or get_build_configuration_value. I couldn't
> think of an alternative to the word "build" to represent a certain
> installed version of Texinfo but there might be one.
Let's go with get_build_constant,
On Sun, Jan 28, 2024 at 09:13:21PM +0100, Patrice Dumas wrote:
> On Sat, Jan 27, 2024 at 05:55:24PM +, Gavin Smith wrote:
> > The get_constant function has been recently added but I think the name of
> > this is too generic.
>
> Any idea on another name?
It reminds me of the output of perl
On Sat, Jan 27, 2024 at 05:55:24PM +, Gavin Smith wrote:
> The get_constant function has been recently added but I think the name of
> this is too generic.
Any idea on another name?
--
Pat
On Sun, Jan 28, 2024 at 12:16:42AM +, Gavin Smith wrote:
> > If there is still a customization variable to access for this, then
> > I don't see why the name has to be changed. I haven't had any new thoughts
> > on this since my previous emails on the topic, I'm afraid. I remember
> > that
On Sat, Jan 27, 2024 at 06:47:24PM +, Gavin Smith wrote:
> On Sat, Jan 27, 2024 at 07:20:05PM +0100, Patrice Dumas wrote:
> > > I don't know how ffmpeg or other packages are supposed to adapt to the
> > > new interface. Perhaps we could put special case code in get_conf to
> > > check for
On Sat, Jan 27, 2024 at 07:20:05PM +0100, Patrice Dumas wrote:
> > I don't know how ffmpeg or other packages are supposed to adapt to the
> > new interface. Perhaps we could put special case code in get_conf to
> > check for "PACKAGE_VERSION" and redirect to the new interface?
>
> That seems
On Sat, Jan 27, 2024 at 05:55:24PM +, Gavin Smith wrote:
> On Sat, Jan 27, 2024 at 04:26:10PM +0100, Patrice Dumas wrote:
> > I have added a new interface in the version in development to get the
> > PACKAGE_VERSION and other PACKAGE* variables as set by configure:
> >
> > my $texinfo_version
On Sat, Jan 27, 2024 at 04:26:10PM +0100, Patrice Dumas wrote:
> Hello,
>
> On Sun, Nov 05, 2023 at 12:13:00PM +0100, Arsen Arsenović wrote:
> >
> > Patrice Dumas writes:
> >
> > > my $texinfo_version = texinfo_get_conf('PACKAGE_VERSION');
> > > $texinfo_version =~ s/\+dev$//;
> > > #
Hello,
On Sun, Nov 05, 2023 at 12:13:00PM +0100, Arsen Arsenović wrote:
>
> Patrice Dumas writes:
>
> > my $texinfo_version = texinfo_get_conf('PACKAGE_VERSION');
> > $texinfo_version =~ s/\+dev$//;
> > # determine if texinfo is at least version 6.8
> > my $program_version_num =
On Mon, Nov 06, 2023 at 12:21:40PM +0100, Arsen Arsenović wrote:
> Thanks for the review, I've fixed those up. I'll see about sending it
> upstream in when I have enough time to thoroughly test.
>
> Have a lovely day!
Thanks for working on this. It seems to me that a customization API
could
Hi Patrice,
Patrice Dumas writes:
> On Sun, Nov 05, 2023 at 12:13:00PM +0100, Arsen Arsenović wrote:
>>
>> Seems that relatively many things changed between 6.x and 7.0.
>
> 7.0 was the first release with an official HTML customization API. The
> API is not stable yet, as the many changes
Patrice Dumas writes:
> On Sat, Nov 04, 2023 at 02:39:32PM +0100, Arsen Arsenović wrote:
>> Afternoon,
>>
>> Following changes in Texinfo 7.1 (uncertain which commit - haven't
>> bisected) FFmpeg documentation no longer builds. This is due to an init
>> file (attached). The following is a
On Sun, Nov 05, 2023 at 12:13:00PM +0100, Arsen Arsenović wrote:
>
> Seems that relatively many things changed between 6.x and 7.0.
7.0 was the first release with an official HTML customization API. The
API is not stable yet, as the many changes between 7.0 and 7.1 and the
changes already in
On Sat, Nov 04, 2023 at 02:39:32PM +0100, Arsen Arsenović wrote:
> Afternoon,
>
> Following changes in Texinfo 7.1 (uncertain which commit - haven't
> bisected) FFmpeg documentation no longer builds. This is due to an init
> file (attached). The following is a minimum reproducer:
>
>
14 matches
Mail list logo
