mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Roland Hieber <rhi@pengutronix.de>
Subject: Re: [ptxdist] [APPLIED] vim: prevent file name conflicts with busybox
Date: Wed, 12 Apr 2023 08:29:52 +0200	[thread overview]
Message-ID: <20230412062952.3435439-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20230404210435.3363032-1-rhi@pengutronix.de>

Thanks, applied as ad2eb34a07ed0ba8868bcf2341555ed59e02ea4a.

Michael

[sent from post-receive hook]

On Wed, 12 Apr 2023 08:29:52 +0200, Roland Hieber <rhi@pengutronix.de> wrote:
> Busybox can install both xxd and vi, which will conflict with the files
> installed by the vim package. If both busybox tools are selected, don't
> make the vim menu selectable at all, otherwise make only the tools
> selectable that are not installed by busybox.
> 
> Signed-off-by: Roland Hieber <rhi@pengutronix.de>
> Message-Id: <20230404210435.3363032-1-rhi@pengutronix.de>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
> 
> diff --git a/rules/vim.in b/rules/vim.in
> index f09b93b47cfd..c4c9d14e6833 100644
> --- a/rules/vim.in
> +++ b/rules/vim.in
> @@ -1,7 +1,11 @@
>  ## SECTION=editors
>  
> +comment "BusyBox' vi and xxd is selected!"
> +	depends on BUSYBOX_VI && BUSYBOX_XXD
> +
>  menuconfig VIM
>  	tristate
> +	depends on !(BUSYBOX_VI && BUSYBOX_XXD)
>  	select LIBC_DL
>  	select LIBC_M
>  	select GCCLIBS_GCC_S
> @@ -14,10 +18,18 @@ menuconfig VIM
>  
>  if VIM
>  
> +comment "BusyBox' vi is selected!"
> +	depends on BUSYBOX_VI
> +
>  config VIM_VIM
> +	depends on !BUSYBOX_VI
>  	bool "Vim Editor"
>  
> +comment "BusyBox' xxd is selected!"
> +	depends on BUSYBOX_XXD
> +
>  config VIM_XXD
> +	depends on !BUSYBOX_XXD
>  	bool "XXD"
>  
>  endif



      reply	other threads:[~2023-04-12  6:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-04 21:04 [ptxdist] [PATCH] " Roland Hieber
2023-04-12  6:29 ` Michael Olbrich [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=20230412062952.3435439-1-m.olbrich@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    --cc=rhi@pengutronix.de \
    /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