vim.inc - when you don't use vim-tiny, you get vim-big

[Duisenberg, Ken]

I got my vim recipe from:
https://layers.openembedded.org/layerindex/recipe/96649/

 

I posted this at vi.stackexchange.com:

https://vi.stackexchange.com/questions/48653/building-vim-small-gets-with-features-big-added

but they said vim.inc is not part of github, so I came here.

 

I see Christian posted this in my stackexchange question
That is certainly not a diff for github Vim repo. We don't ship such a file recipes-support/vim/vim.inc. I am guessing this might be some homebrew repo? Also please note, that vim-small and vim-big have officially been retired as of v9.0.0657 and v9.0.0700 

– Christian Brabandt

 CommentedMay 16 at 15:40

 

… but it still looks like a bug in the layer to me.  Is it not?

 

Issue:

I discovered when building 9.2.0340 vim-small, it includes the --with-features=big. This is due to vim.inc PACKAGECONFIG[tiny] including that flag when "tiny" is not included. Here is a patch that fixes this. I tried searching to see if there's already a patch, but didn't see one.  I was actually trying to use the –with-features=small, but because I didn’t include “tiny”, I got both small and big in my variables.

 

As for retiring vim-small, what it the expected method for effectively building with less features?  Building small still worked, so is it deprecated? 

 

I created this patch below to avoid getting the “big” flag, but is there a better approach? Or is “tiny” the only other option than “big” now?

 

Thanks for any pointers.

 

Ken Duisenberg

---

meta/recipes-support/vim/vim.inc | 2 +-

1 file changed, 1 insertion(+), 1 deletion(-)

 

diff --git a/meta/recipes-support/vim/vim.inc b/meta/recipes-support/vim/vim.inc

index d6fdf45706..1c77f8cb6c 100644

--- a/meta/recipes-support/vim/vim.inc

+++ b/meta/recipes-support/vim/vim.inc

@@ -60,7 +60,7 @@ PACKAGECONFIG ??= "\

PACKAGECONFIG[gtkgui] = "--enable-gui=gtk3,--enable-gui=no,gtk+3"

PACKAGECONFIG[acl] = "--enable-acl,--disable-acl,acl,"

PACKAGECONFIG[x11] = "--with-x,--without-x,xt,"

-PACKAGECONFIG[tiny] = "--with-features=tiny,--with-features=big,,"

+PACKAGECONFIG[tiny] = "--with-features=tiny,,,"

PACKAGECONFIG[selinux] = "--enable-selinux,--disable-selinux,libselinux,"

PACKAGECONFIG[elfutils] = "--enable-elf-check,,elfutils,"

PACKAGECONFIG[nls] = "--enable-nls,--disable-nls,,"

 

[Christian Brabandt]

On Di, 19 Mai 2026, 'Duisenberg, Ken' via vim_dev wrote:

> I got my vim recipe from:
> https://layers.openembedded.org/layerindex/recipe/96649/

I have no idea what this is or why you need a vim recipe.

> I posted this at vi.stackexchange.com:
> https://vi.stackexchange.com/questions/48653/building-vim-small-gets-with-features-big-added
> but they said vim.inc is not part of github, so I came here.
>
> I see Christian posted this in my stackexchange question
> That is certainly not a diff for github Vim repo. We don't ship such a file recipes-support/vim/vim.inc. I am guessing this might be some homebrew repo? Also please note, that vim-small and vim-big have officially been retired as of v9.0.0657 and v9.0.0700

> - Christian Brabandt<https://vi.stackexchange.com/users/71/christian-brabandt>
> CommentedMay 16 at 15:40<https://vi.stackexchange.com/questions/48653/building-vim-small-gets-with-features-big-added#comment88738_48653>
>
> ... but it still looks like a bug in the layer to me. Is it not?

Possibly, but not for us. We are not related in any way to the webpage
that provided that "recipe". That needs to be fixed by whoever created
that recipe. You should report it at the websites issue tracker or
maintainer/contact.

> I discovered when building 9.2.0340 vim-small, it includes the
> --with-features=big. This is due to vim.inc PACKAGECONFIG[tiny]
> including that flag when "tiny" is not included. Here is a patch that
> fixes this. I tried searching to see if there's already a patch, but
> didn't see one. I was actually trying to use the

> -with-features=small, but because I didn't include "tiny", I got both

> small and big in my variables.
>
> As for retiring vim-small, what it the expected method for effectively
> building with less features? Building small still worked, so is it
> deprecated?

The reason for retiring vim-small was, that the feature set between
vim-small and vim-tiny was so small, that this distinction no longer
made sense. Either use vim-tiny if you want a small vim, or enable
specific flags directly using the configure script.


Best,
Christian
--
There is a natural hootchy-kootchy to a goldfish.
-- Walt Disney