[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240312142420.53e35ab4@hermes.local>
Date: Tue, 12 Mar 2024 14:24:20 -0700
From: Stephen Hemminger <stephen@...workplumber.org>
To: Max Gautier <mg@....gautier.name>
Cc: netdev@...r.kernel.org
Subject: Re: [PATCH iproute2-next] Makefile: use systemd-tmpfiles to create
/var/lib/arpd
On Tue, 12 Mar 2024 09:22:20 +0100
Max Gautier <mg@....gautier.name> wrote:
> On Mon, Mar 11, 2024 at 06:30:07PM -0700, Stephen Hemminger wrote:
> > On Mon, 11 Mar 2024 23:28:31 +0100
> > Max Gautier <mg@....gautier.name> wrote:
> >
> > > On Mon, Mar 11, 2024 at 12:40:03PM -0700, Stephen Hemminger wrote:
> > > > On Mon, 11 Mar 2024 17:57:27 +0100
> > > > Max Gautier <mg@....gautier.name> wrote:
> > > >
> > > > > Only apply on systemd systems (detected in the configure script).
> > > > > The motivation is to build distributions packages without /var to go
> > > > > towards stateless systems, see link below (TL;DR: provisionning anything
> > > > > outside of /usr on boot).
> > > > >
> > > > > The feature flag can be overridden on make invocation:
> > > > > `make USE_TMPFILES_D=n DESTDIR=<install_loc> install`
> > > > >
> > > > > Links: https://0pointer.net/blog/projects/stateless.html
> > > >
> > > > Why does arpd need such hand holding, it is rarely used, maybe should just not be built.
> > >
> > > The commit introducing the install of that directory is quite old
> >
> > The problem is that build environment != runtime environment for embedded systems.
>
> That's the same for anything detected by the configure script, right ?
> Hence the override capability.
Configure is mostly about what packages are missing from the build.
It would be better if arpd was just smarter about where to put its
file.
>
> > But arpd really is legacy/dead/rotting code at this point.
>
> Yeah I can see that, not touched since 2016 (mostly). You would rather
> just drop it ?
>
Powered by blists - more mailing lists