From: Martin Jansa <martin.jansa@gmail.com>
To: Michael Smith <msmith@cbnco.com>
Cc: openembedded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: nano RRECOMMENDS ncurses-terminfo
Date: Sat, 25 Sep 2010 00:02:56 +0200 [thread overview]
Message-ID: <20100924220256.GA3423@jama> (raw)
In-Reply-To: <4C9D0872.5060404@cbnco.com>
On Fri, Sep 24, 2010 at 04:22:10PM -0400, Michael Smith wrote:
> Hi,
>
> Since 37df6011, nano recommends ncurses-terminfo.
>
> +# actually RDEPENDS, but ncurses-terminfo is only in ncurses-5.7, so
> RRECOMMENDS for now
> +RRECOMMENDS_${PN} = "ncurses-terminfo"
>
> ncurses-terminfo exists in 5.4: it contains 2.4 MB of terminfo data
> files that is just bloat for most people. (Then again, you could say
> nano is also just bloat. :) The base ncurses-5.4 package includes some
> common terminfo files in /etc/terminfo.
>
> So for me, with ncurses 5.4, nano shouldn't depend on or recommend
> ncurses-terminfo - it just bloats up the image.
>
> Is there something special in ncurses-terminfo 5.7 that nano needs?
There wasn't any common /etc/terminfo in base ncurses-5.7 package and I
guess it's still isn't. So nano refused to start at all (like other apps
where I added this RRECOMMENDS after we switched to 5.7 and apps started
to fail.
If it's so big problem then please improve ncurses-5.7 recipe to include
most common terminfos and then feel free to drop those RRECOMMENDS I've
added. Or just move to newer ncurses (ie because of problems with newer
distributions on buildhost, also discussed here).
Regards,
> Thanks,
> Mike
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
next prev parent reply other threads:[~2010-09-24 22:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-24 20:22 nano RRECOMMENDS ncurses-terminfo Michael Smith
2010-09-24 22:02 ` Martin Jansa [this message]
2010-09-25 13:56 ` Enrico Scholz
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=20100924220256.GA3423@jama \
--to=martin.jansa@gmail.com \
--cc=msmith@cbnco.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.