Bug 252805 - devel/notcurses: allow using base ncurses
Summary: devel/notcurses: allow using base ncurses
Status: Closed Not Accepted
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: Steve Wills
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-01-18 13:48 UTC by Steve Wills
Modified: 2021-01-19 22:18 UTC (History)
1 user (show)

See Also:
bugzilla: maintainer-feedback? (nickblack)


Attachments
patch to make ports ncurses optional (1.73 KB, patch)
2021-01-18 13:48 UTC, Steve Wills
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Steve Wills freebsd_committer 2021-01-18 13:48:10 UTC
Created attachment 221707 [details]
patch to make ports ncurses optional

Ncurses is in base, but doesn't have a pkg-config file in base. Base ncurses is newer in newer releases. This patch allows using it if ports ncurses isn't installed.
Comment 1 Nick Black 2021-01-18 18:41:43 UTC
Comment on attachment 221707 [details]
patch to make ports ncurses optional

Seems reasonable to me, though I'm admittedly unsure what the difference is between the in-Base ncurses and ncurses Port. All I need from either is a working terminfo library and database.

If `notcurses-tester` and `notcurses-demo` still work well following this change, go for it!
Comment 2 Steve Wills freebsd_committer 2021-01-19 20:27:51 UTC
(In reply to Nick Black from comment #1)
Thanks for pointing those out. I discovered a problem in my port Makefile patch, which I fixed, which lead me to discover that the base libtinfo is a symlink to the base libncursesw which contains conflicting symbols with notcurses, so this may not be workable for now.
Comment 3 Steve Wills freebsd_committer 2021-01-19 22:18:07 UTC
This just isn't workable right now. Maybe if we can fix ncurses in base we can revisit this another time. Closing for now.