From: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: libtermcap
Date: Wed, 08 Sep 2010 22:16:19 +0200 [thread overview]
Message-ID: <ly39tkkn3g.fsf@ensc-virt.intern.sigma-chemnitz.de> (raw)
In-Reply-To: <4C87E05A.6050004@mentor.com> (Tom Rini's message of "Wed, 08 Sep 2010 12:13:30 -0700")
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!'
> 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.
Enrico
next prev parent reply other threads:[~2010-09-08 20:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-06 17:50 libtermcap (was: Re: Asterisk and termcap) Frans Meulenbroeks
2010-09-06 20:34 ` Arigead
2010-09-06 20:50 ` Frans Meulenbroeks
2010-09-08 18:48 ` libtermcap Enrico Scholz
2010-09-08 19:13 ` libtermcap Tom Rini
2010-09-08 20:16 ` Enrico Scholz [this message]
2010-09-08 20:24 ` libtermcap Tom Rini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ly39tkkn3g.fsf@ensc-virt.intern.sigma-chemnitz.de \
--to=enrico.scholz@sigma-chemnitz.de \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox