Re: libtermcap

[Tom Rini <tom_rini@mentor.com>]

Enrico Scholz wrote:
> Tom Rini <tom_rini@mentor.com> writes:
> 
>>> I added 9e58422868a03eeafa72781477174850d1c5abe7 some hours ago so
>>> that '-ltermcap' should work again.  Patch does not break my builds
>>> but I do not know whether it unbreaks the problematic ones ;)
>>>
>>> Things are too different across the distributions (some have the
>>> ncurses-config binconfig tools, other the .pc files, some have
>>> libtinfo, some not) to find *the* correct solution.
>> Maybe I'm jumping in too late here.  Why is the correct solution not
>> "make our ncurses-native build and install what's required by other
>> recipes, fix broken recipes that look for the wrong thing" ?  
> 
> the "wrong" and "right" thing is difficultly to define for libtermcap.
> Generally, patches should be in a manner that they can be accepted by
> upstream.  That's not the case for 's!-ltermcap!-ltinfo!'

Now that you've added a libtermcap + deprecated warning, that problem 
should be solved, yes?  What I'm saying is that we build ncurses 5.7 for 
the host system.  What we build there is what other programs we build 
should be looking for and using.  If they're looking for something we 
don't provide, that's a problem we should fix.  It should not ever 
matter what the host distribution provides as using it is wrong unless 
ASSUME_PROVIDED is set and in that case, it's user be aware.

>> IMHO, if you ASSUME_PROVIDED and things break, thats not our problem,
>> its your problem (Doctor, it hurts when I do *this*.  Don't do *that*
>> !)
> 
> OE has still the ncurses-5.4 receipt which will break packages depending
> on hardcoded -ltinfo.

Which should probably get dropped once everything is happy with 5.7.

-- 
Tom Rini
Mentor Graphics Corporation