[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAASaF6wcW54MwR-CdR_bfXRJS+ar0y87g7FN1_T6qLVJX0Ti6A@mail.gmail.com>
Date: Wed, 11 Dec 2024 13:42:28 +0100
From: Jan Stancek <jstancek@...hat.com>
To: Donald Hunter <donald.hunter@...il.com>, Jakub Kicinski <kuba@...nel.org>
Cc: stfomichev@...il.com, pabeni@...hat.com, davem@...emloft.net,
edumazet@...gle.com, horms@...nel.org, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 2/5] tools: ynl: provide symlinks to user-facing
scripts for compatibility
On Wed, Dec 11, 2024 at 10:21 AM Donald Hunter <donald.hunter@...il.com> wrote:
>
> On Wed, 11 Dec 2024 at 03:26, Jakub Kicinski <kuba@...nel.org> wrote:
> >
> > On Mon, 9 Dec 2024 15:47:14 +0100 Jan Stancek wrote:
> > > For backwards compatibility provide also symlinks from original location
> > > of user facing scripts.
> >
> > Did someone ask for this? Does everything work without the symlinks?
> > If the answers are "no", "yes" then let's try without this patch.
> > In tree users should be able to adjust.
>
> I asked for the symlinks for cli.py and ethtool.py to avoid surprising
> people when they move. The ynl-gen- scripts are primarily used in-tree
> via Makefiles so I didn't think they should be symlinked. Happy to go
> with your suggestion to drop this if you'd prefer not to have any
> symlinks.
I'll drop them, we can always add them later in case someone
_really_ needs original script locations.
>
> Thanks,
> Donald
>
Powered by blists - more mailing lists