From: Tom Rini <trini@konsulko.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] vim: Rework things so vim adds features not vim-tiny removes
Date: Sat, 18 May 2019 20:13:28 -0400 [thread overview]
Message-ID: <20190519001328.GM22232@bill-the-cat> (raw)
In-Reply-To: <20190518190327.GL22232@bill-the-cat>
[-- Attachment #1: Type: text/plain, Size: 1298 bytes --]
On Sat, May 18, 2019 at 03:03:27PM -0400, Tom Rini wrote:
> On Sat, May 18, 2019 at 08:57:02PM +0200, Martin Jansa wrote:
> > Thanks Tom for quick update.
> >
> > ALTERNATIVE_TARGET[xxd] = "${bindir}/xxd"
> > ALTERNATIVE_LINK_NAME[xxd] = "${bindir}/xxd"
> > looks strange, IIRC TARGET and LINK_NAME should always point to different
> > filepath, it was added in meta-oe commit:
> >
> > commit 897c10b7c17c138a85bdeb36cf72e7201daf0e0e
> > Author: Dan McGregor <dan.mcgregor@usask.ca>
> > Date: Thu Oct 18 09:46:27 2018 -0600
> >
> > vim: alternatify xxd
> >
> > toybox also provides xxd.
> >
> > but I wonder what u-a does (or is supposed to do in this scenario). Maybe
> > u-a bbclass automatically adds .${BPN} suffix to TARGET and renames the
> > installed file?
>
> I'll double check, but also toybox doesn't have anything for xxd today,
> so I'll add that into my build and come up with something sane for both
> if needed, thanks!
OK, so busybox, toybox and vim all provide "xxd" and busybox/toybox
setup u-a with their normal method. With what vim has (today and also
with this patch) we end up with /usr/bin/xxd.vim, which is what we want.
I inspected the ipk for that, and then putting all 3 in
core-image-minimal looks sane too.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2019-05-19 0:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-17 13:53 [PATCH] vim: split the common part into vim.inc Alexander Kanavin
2019-05-17 14:27 ` Martin Jansa
2019-05-17 14:29 ` Martin Jansa
2019-05-17 14:34 ` Alexander Kanavin
2019-05-18 11:35 ` Tom Rini
2019-05-18 14:46 ` Alexander Kanavin
2019-05-18 18:34 ` [PATCH] vim: Rework things so vim adds features not vim-tiny removes Tom Rini
2019-05-18 18:57 ` Martin Jansa
2019-05-18 19:03 ` Tom Rini
2019-05-19 0:13 ` Tom Rini [this message]
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=20190519001328.GM22232@bill-the-cat \
--to=trini@konsulko.com \
--cc=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.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