public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Alan Perry" <alanp@snowmoose.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
	openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH v2 1/2] iproute2: install tools to mirror install under Debian/Ubuntu
Date: Wed, 9 Dec 2020 14:39:22 -0800	[thread overview]
Message-ID: <83ae3fae-37a5-e32d-5084-e1a20d97b13d@snowmoose.com> (raw)
In-Reply-To: <bb38bb9111dbc5e0a2c3c47256d2bead31b70316.camel@linuxfoundation.org>



On 12/7/20 1:49 PM, Richard Purdie wrote:
> On Sat, 2020-12-05 at 08:22 +0000, Alan Perry wrote:
>> Many scripts exist that expect the iproute2 tools to be found in
>> the same directories where they are found in Debian or Ubuntu.
>> For the iproute2 tools included in the iproute2 recipe, move
>> them to those directories or create links there.. Also, add
>> bash-completion files as is done by Debian and Ubuntu.
>>
>> Signed-off-by: Alan Perry <alanp@snowmoose.com>
>> ---
>>   .../iproute2/iproute2.inc                     | 23 +++++++++++++++++--
>>   1 file changed, 21 insertions(+), 2 deletions(-)
> The direction in the patch is worrying me a little.
>
> There is a bash-completion class which splits completion files into
> their own package, most "embedded" users don't want them in the main
> packages. This patch does something different to what has been done
> elsewhere.
>
> Secondly, I'm also not sure that just because debian does something we
> should therefore do it, I'm not convinced that scripts should be
> hardcoding path assumptions about these tools. IF this is such a
> universal need, why doesn't upstream change the default installation
> locations? Has it been discussed?
>
> I'd expect there to be opinions on this topic but I'm not seeing much
> discussion. I suspect if if does merge there would be push back later
> though.
>
> Also, the duplication between bin and sbin for ip is not particularly
> good practise.
>
Thanks for your comments. I apologize for the delay in responding, but I 
needed to do some research first.

I will look at the bash-completion class and make the appropriate 
changes there.

As far as the installation path changes, I discussed why those aren't 
the defaults with the iproute2 upstream maintainer. The idea is that the 
upstream puts everything in /sbin and where is appropriate to install 
them for a given distro is left as an exercise for that distro.

The iproute2 recipe is doing that exercise for poky. So, where is the 
correct place to install these tools on poky? I'd argue that they should 
go in the expected directories for Unix-y OSes. Someone at Debian went 
through that analysis and put them where they put them and those mostly 
seem like reasonable places to me. It is also where users coming to 
poky-based systems will likely expecting to find them.

As far as duplicating ip in bin and sbin, I agree that it isn't good 
practice. Having it in both doesn't seem necessary to me.

alan


  reply	other threads:[~2020-12-09 22:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-05  8:22 [PATCH v2 1/2] iproute2: install tools to mirror install under Debian/Ubuntu Alan Perry
2020-12-05  8:22 ` [PATCH v2 2/2] iproute2: rearrange FILES to improve readability Alan Perry
2020-12-07 21:49 ` [OE-core] [PATCH v2 1/2] iproute2: install tools to mirror install under Debian/Ubuntu Richard Purdie
2020-12-09 22:39   ` Alan Perry [this message]
2020-12-09 23:40     ` Andre McCurdy
2020-12-10  0:00       ` Alan Perry

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83ae3fae-37a5-e32d-5084-e1a20d97b13d@snowmoose.com \
    --to=alanp@snowmoose.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox