git: 620f205539a4 - main - editors/vim: Flavorize and update to 8.2.3394

Adam Weinberger adamw at freebsd.org
Thu Sep 2 18:12:43 UTC 2021


On Thu, Sep 2, 2021 at 9:57 AM Michael Gmelin <grembo at freebsd.org> wrote:

>
>
> On Thu, 2 Sep 2021 17:46:35 +0200
> Michael Gmelin <grembo at freebsd.org> wrote:
>
> > On Thu, 2 Sep 2021 15:22:53 +0000
> > Colin Percival <cperciva at tarsnap.com> wrote:
> >
> > > On 9/1/21 11:46 PM, Adam Weinberger wrote:
> > > > URL:
> > > >
> https://cgit.FreeBSD.org/ports/commit/?id=620f205539a43fd8da97750d33eebdfc1e133330
> > > >
> > > > commit 620f205539a43fd8da97750d33eebdfc1e133330
> > > > Author:     Adam Weinberger <adamw at FreeBSD.org>
> > > > AuthorDate: 2021-09-02 06:36:47 +0000
> > > > Commit:     Adam Weinberger <adamw at FreeBSD.org>
> > > > CommitDate: 2021-09-02 06:36:47 +0000
> > > >
> > > >     editors/vim: Flavorize and update to 8.2.3394
> > > >
> > > >     This commit completely rewires the vim ports. It includes the
> > > > following:
> > >
> > > `make index` is now failing with
> > > /usr/ports/audio/fluida-lv2: no entry for
> > > /usr/ports/editors/vim-console
> > >
> > > I'm not sure if this is because INDEX doesn't understand flavours or
> > > if you need to adjust port(s) which depend on vim-console.
> > >
> >
> > The problem with using flavors like this is that it basically turns
> > those ports into leaf ports (as you, e.g., can't install a port that
> > relies on vim-tiny and install vim-gtk3 at the same time).
> >
> > We have the same situation with git-lite, git, git-svn, git-cvs...
> > That's why, e.g., iocage depends on git and not on git-lite (which
> > would be sufficient), as every time you install normal git, iocage
> > would get removed from the system.
> >
> > Subpackages would solve this (but they're not here yet).
> >
> > One can emulate subpackages by creating subports using MASTERDIR. I
> > did this for git a while ago (review pending due to lack of
> > resources):
> >
> > https://reviews.freebsd.org/D30238
> >
>
> To be fair, before we had conflicting ports, which wasn't better.
>
> @cperciva fixing the problem you actually asked about is probably as
> simple as changing
>
>   /usr/ports/editors/vim-console
>
> to
>
>   /usr/ports/editors/vim at console
>
> in the affected ports.
>

Thanks, all, for the ping on this. I changed it to editors/vim, not
vim at console, because all (non-tiny) vim packages contain the vim and/or xxd
binaries. I think that's the right approach?

# Adam


-- 
Adam Weinberger
adamw at adamw.org // adamw at FreeBSD.org
https://www.adamw.org


More information about the dev-commits-ports-main mailing list