--- Begin Message ---
On Jan 7, 2023, at 8:51 AM, Denis Ovsienko wrote:
> On Fri, 6 Jan 2023 17:13:20 -0800
> Guy Harris wrote:
>
>> On Jan 6, 2023, at 3:31 PM, Denis Ovsienko
>> wrote:
>>
>>> It is the latter, and a custom Autoconf seems an unreasonable
>>> requirement for contributing.
--- Begin Message ---
On 07/01/2023 20:13, Michael Richardson wrote:
>
> Francois-Xavier Le Bail via tcpdump-workers wrote:
> > Or don't generate it and have the build process be:
> > ./autogen.sh && ./configure && ...
>
> That just leads to non-deterministic builds for everyone :-(
--- Begin Message ---
On 06/01/2023 21:38, Francois-Xavier Le Bail via tcpdump-workers wrote:
>> As some have experienced before, attempts to regenerate the configure
>> script often result in two groups of unnecessary changes (runstatedir
>> and LARGE_OFF_T), both of which come from
--- Begin Message ---
On Sat, Jan 7, 2023 at 12:38 PM Denis Ovsienko wrote:
> On Wed, 4 Jan 2023 08:40:21 -0500
> Bill Fenner via tcpdump-workers
> wrote:
>
> > Hi,
> >
> > I know the tcpdump style follows a bunch of bsd patterns, since it
> > came from Berkeley in the first place. Does anyone
--- Begin Message ---
On Wed, 4 Jan 2023 08:40:21 -0500
Bill Fenner via tcpdump-workers
wrote:
> Hi,
>
> I know the tcpdump style follows a bunch of bsd patterns, since it
> came from Berkeley in the first place. Does anyone have a
> clang-format config that reflects these coding conventions?
--- Begin Message ---
On Fri, 6 Jan 2023 17:13:20 -0800
Guy Harris wrote:
> On Jan 6, 2023, at 3:31 PM, Denis Ovsienko
> wrote:
>
> > It is the latter, and a custom Autoconf seems an unreasonable
> > requirement for contributing.
>
> Reasonable, or unreasonable?
Unreasonable, if it is more
--- Begin Message ---
On 06/01/2023 23:49, Guy Harris via tcpdump-workers wrote:
> An alternative would be *not* to keep the generated configure script in the
> repository (that's what Wireshark ended up doing before it ceased to use
> autoconf/automake), and generate it as part of the
