Re: [voidlinux/void-packages] [WIP] New package: vimpager-2.06 (#5554)

ivierlin at Wed, 18 Jan 2017 09:34:57 -0800
So should I leave it like that? It's kind of obvious `vimpager` needs some form of `vim`. On the other hand resolving dependencies is half the fun in using a package manager at all.
Jürgen Buchmüller at Wed, 18 Jan 2017 10:02:03 -0800
You can just add an `INSTALL.msg` file telling the user to install either `vim` or `neovim`, too.
Anachron at Wed, 18 Jan 2017 20:59:29 -0800
I think an "dependsonany='vim neovim ...'" would not be a bad idea after all. If someone uninstalls vim the pkg-manager could then pick up the useless parent-pkg if none dependsonany are remaining. This could be done to many more packages.
ivierlin at Thu, 19 Jan 2017 04:06:02 -0800
Or we simply use `build_options` for that? There is a `$(vopt_if <option> <pkg>)` parser anyway. In this case set `build_options_default` to `vim` and provide `neovim` as option. That's the beauty of a binary/source model. Provide sensible default binaries and make it easy to change them.
Anachron at Thu, 19 Jan 2017 04:18:28 -0800
Not a bad idea. XBPS would still not realize that vimpager is useless without vim/neovim though, right?
ivierlin at Thu, 19 Jan 2017 05:07:11 -0800
It would. Have a look in the template I just pushed. Should be self explaining. The package now depends on vim unless you rebuild it with `-o neovim`. I think that's the most sane option?
Anachron at Thu, 19 Jan 2017 06:20:42 -0800
Ah, now that is a good idea! I somehow didn't realize you could just `vopt` on `depends` too.
Toyam Cox at Tue, 24 Jan 2017 13:31:18 -0800
Closed #5554 via 38afeb88f8c3ea8c50fe79cfaf13b4ad10b9274e.