From: Alexander Dahl <ada@thorsis.com>
To: Ian Abbott <abbotti@mev.co.uk>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] vim: allow vim to be installed alongside busybox vi and xxd
Date: Fri, 3 May 2024 11:40:46 +0200 [thread overview]
Message-ID: <20240503-amiss-veteran-105160060dfa@thorsis.com> (raw)
In-Reply-To: <f002389b-9c5b-493d-a573-b0036bb5b272@mev.co.uk>
Hello Ian,
Am Fri, May 03, 2024 at 10:12:47AM +0100 schrieb Ian Abbott:
> On 03/05/2024 07:59, Alexander Dahl wrote:
> > Hello Ian,
> >
> > I like the idea. Maybe it confuses users if 'vi' calls busybox and
> > 'vim' the full featured Vim, but I appreciate it anyway. More
> > feedback below.
>
> Thanks for the review. Feedback below.
>
> > Am Thu, May 02, 2024 at 03:53:22PM +0100 schrieb Ian Abbott:
> > > --- a/rules/vim.in
> > > +++ b/rules/vim.in
> > > @@ -1,15 +1,7 @@
> > > ## 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
> > > - select NCURSES
> > > prompt "vim "
> > > help
> > > Vim is an advanced text editor that seeks to provide the
> > > @@ -18,12 +10,20 @@ menuconfig VIM
> > > if VIM
> > > -comment "BusyBox' vi is selected!"
> > > - depends on BUSYBOX_VI
> > > -
> > > config VIM_VIM
> > > - depends on !BUSYBOX_VI
> > > bool "Vim Editor"
> > > + select LIBC_DL
> > > + select LIBC_M
> > > + select GCCLIBS_GCC_S
> > > + select NCURSES
> >
> > Don't move this to the suboption, keep it in the original place but
> > add 'if VIM_VIM' like this:
> >
> > select LIBC_DL if VIM_VIM
> >
> > This avoids dependency problems, it's also in documentation:
> > https://www.ptxdist.org/doc/dev_advanced_rule_files.html#managing-external-compile-time-dependencies-on-demand
>
> OK, that makes sense.
>
> > > +
> > > +comment "BusyBox' vi is selected!"
> > > + depends on VIM_VIM && BUSYBOX_VI
> > > +
> > > +config VIM_VI_SYMLINK
> > > + depends on VIM_VIM && !BUSYBOX_VI
> >
> > The !BUSYBOX_VI is redundant, but I guess one can keep it.
>
> I'm not sure why it's redundant. I don't want this option and BUSYBOX_VI
> fighting over the symlink to /usr/bin/vi in the image.
Right, there should be only one package setting that symlink.
What I meant was: VIM_VIM already depends on !BUSYBOX_VI so if
VIM_VI_SYMLINK depends on VIM_VIM, then !BUSYBOX_VI is already
implicitly satisfied and stating it again is not strictly necessary.
IMHO: Keep it in, it better reflects the intention.
Greets
Alex
>
> >
> > Greets
> > Alex
> >
> > > + bool "install symbolic link /usr/bin/vi"
> > > + default y
> > > comment "BusyBox' xxd is selected!"
> > > depends on BUSYBOX_XXD
> > > diff --git a/rules/vim.make b/rules/vim.make
> > > index b03778e53..8700b70bd 100644
> > > --- a/rules/vim.make
> > > +++ b/rules/vim.make
> > > @@ -103,6 +103,10 @@ VIM_INSTALL_OPT := \
> > > VIM_LINKS := ex rview rvim view vimdiff
> > > +ifdef PTXCONF_VIM_VI_SYMLINK
> > > +VIM_LINKS += vi
> > > +endif
> > > +
> > > $(STATEDIR)/vim.targetinstall:
> > > @$(call targetinfo)
> > > --
> > > 2.43.0
> > >
> > >
>
> Thanks again. I'll submit a v2 patch shortly.
>
> --
> -=( Ian Abbott <abbotti@mev.co.uk> || MEV Ltd. is a company )=-
> -=( registered in England & Wales. Regd. number: 02862268. )=-
> -=( Regd. addr.: S11 & 12 Building 67, Europa Business Park, )=-
> -=( Bird Hall Lane, STOCKPORT, SK3 0XA, UK. || www.mev.co.uk )=-
>
>
next prev parent reply other threads:[~2024-05-03 9:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-02 14:53 Ian Abbott
2024-05-03 6:59 ` Alexander Dahl
2024-05-03 9:12 ` Ian Abbott
2024-05-03 9:40 ` Alexander Dahl [this message]
2024-05-03 12:24 ` Ian Abbott
2024-05-03 12:29 ` Alexander Dahl
2024-05-03 9:14 ` [ptxdist] [PATCH v2] " Ian Abbott
2024-05-03 14:56 ` Michael Olbrich
2024-05-03 18:01 ` [ptxdist] [PATCH v3] " Ian Abbott
2024-05-03 18:08 ` [ptxdist] [PATCH v4] " Ian Abbott
2024-05-12 13:16 ` [ptxdist] [APPLIED] " Michael Olbrich
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=20240503-amiss-veteran-105160060dfa@thorsis.com \
--to=ada@thorsis.com \
--cc=abbotti@mev.co.uk \
--cc=ptxdist@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