New comment by MarleDK on void-packages repository

https://github.com/void-linux/void-packages/pull/21409#issuecomment-620777005

Comment:
> Actually `ncurses-devel` and `tinfo-devel` need to be conflicting packages.

I don't think they should be conflicting. I think the tinfo package should just only provide libtinfo.so*  
But since the ncurses will provide the full ncurses.so* libraries (with both ncurses and tinfo functions), it should be useable by both programs which expect it to provide everything, and programs, which only expect it to provide ncurses without tinfo.

But wouldn't it pose problems leaving it as different packages, especially if they are not updated together? Not by the user, but if ncurses gets its version bumped in the repo, but tinfo does not. 

In the issue #11718 they link to this: https://github.com/commercialhaskell/stack/issues/4711#issuecomment-480614106 
Where it is suggested that some packages simply symlink libtinfo to libncurses. 
Do you think that would be a valid solution? 
In a way it would also be a simpler solution, if libncurses needs all the logic from libtinfo anyway.
I suppose this way it could be made simply by symlinking in ncurses when building, and then create packages which copy the symlinks. 
Or would it then be better just to always include libtinfo symlinked to libncurses?

I will create a new commit where I symlink them, then it should be easy to make it into its own package or include it in ncurses.