Re: Modify ncurses package to provide libtinfo

Re: Modify ncurses package to provide libtinfo

[voidlinux-github]

[-- Attachment #1: Type: text/plain, Size: 254 bytes --]

New comment by anjandev on void-packages repository

https://github.com/void-linux/void-packages/issues/11718#issuecomment-580532140

Comment:
I am trying to update arduino to 1.8.11 and I have the build fails to compile because it can't find **tinfo**.

Re: Modify ncurses package to provide libtinfo

[hasufell]

[-- Attachment #1: Type: text/plain, Size: 230 bytes --]

New comment by hasufell on void-packages repository

https://github.com/void-linux/void-packages/issues/11718#issuecomment-987099385

Comment:
It appears this is fixed and you do:

```sh
xbps-install ncurses-libtinfo-libs
```

Re: [ISSUE] [CLOSED] Modify ncurses package to provide libtinfo

[q66]

[-- Attachment #1: Type: text/plain, Size: 898 bytes --]

Closed issue by lambdadog on void-packages repository

https://github.com/void-linux/void-packages/issues/11718

Description:
This has mostly caused issues in regards to Haskell for me personally, as mentioned in #7403 (although I've also had issues with building several Haskell packages, including Haskeline), but I can only imagine there are issues elsewhere as well.

While it's possible to modify software packaged for Void to use libncurses rather than libtinfo, I assume, when used for a developer system it's often impossible or infeasible to modify all of the software and libraries you're using to conform to Void Linux's choices.

As mentioned in [this comment](https://github.com/commercialhaskell/stack/issues/4711#issuecomment-480614106), most distributions have standardized on providing libtinfo along with libncurses, and I'm of the opinion that Void Linux should follow suit.

Re: Modify ncurses package to provide libtinfo

[bm16ton]

[-- Attachment #1: Type: text/plain, Size: 1510 bytes --]

New comment by bm16ton on void-packages repository

https://github.com/void-linux/void-packages/issues/11718#issuecomment-1763213557

Comment:
I know posting to old threads in forums is considersd rude but it seems like github issues maybe different? If not I truely apologize. Just wanted to say after playing with ncurses crosscompiling for niche hardware and googling I found this and now I think I'm gonna try void linux! (never heard of it b4 just now) Mostly been using homebrew "distros" for past couple years and its always been if the app needed symbols from a specific lib I would point to that lib in Makefile etc for linking all is good even if 2 libs had same symbol. But based of the little I can gather from here if a second lib with same symbol is available then the pkg management being used to compile will fail? Either that or instead of having 2 libs same symbol you dropped one of them and the old now missing lib is what's specified so it fails? Wasn't enuff here for me to get a firm grasp, but its got me curious so I'm gonna give it a go! Package management is such a huge, complicated, endless variation of things, concept that its fun to explore and learn how people greatly (and I do mean greatly!) smarter then myself has implemented it!  Hopefully ill be able to gather some reasoning behind its various design decisions from docs and commits, and hopefully be a better programmer from it..Thank you guys ooensource contributors are truely my heros and seldom praised enuff imho