Second option from my feedback. Is there a way to reuse the ncurses format 1:1, the same directory layout, file format and suffixes? This would make our version a ready drop-in replacement and predictable behavior for $TERMINFO and similar env(1) variables. A benefit of this approach is to reuse existing code in .NET and other potential users of raw terminfo database. The same scenarios for installation of a new files for users etc. It will certainly increase potential for adoption of the NetBSD curses(3) in other systems. On 09.05.2017 22:21, Jaromír Doleček wrote: > I think it would be good to make the database modular, and to stop > requiring having everything in one binary blob. I don't see any > downsides to Roy's suggestion. > > Jaromir > > 2017-05-09 21:48 GMT+02:00 Kamil Rytarowski <n54%gmx.com@localhost>: >> On 09.05.2017 16:50, Roy Marples wrote: >>> On 09/05/2017 12:51, Kamil Rytarowski wrote: >>>> I don't have a preference, but I'm surprised that our single .cdb >>>> approach is going to be hybrid with support for ncurses layout. >>> >>> Other ideas welcome on how to allow pkgsrc to integrate terminfo >>> descriptions. >>> >>> Roy >>> >> >> Are we far from just integrating these custom definitions present today >> in pkgsrc into our base database? They aren't AGPLv3 or similar. Merging >> existing ones and give an option to add a custom one into our base >> terminfo database on demand (MESSAGE for a user) looks liek the best >> option to me. I assume new definitions are rather rarely created. >> >> $TERMINFO could be supported as an alternative (backup, testing, ...) >> .cdb database that could be specified in env(1). >> >> This is a point of view of a user / consumer of terminfo. >>
Attachment:
signature.asc
Description: OpenPGP digital signature