From: "Schenk, Gavin" <G.Schenk@eckelmann.de>
To: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] [PATCH] ncurses: Added /usr/share/terminfo/d/dumb to PTXCONF_NCURSES_TERMCAP
Date: Mon, 8 Feb 2016 07:05:52 +0000 [thread overview]
Message-ID: <D415CD2EC4182C4EAB90A76B7D9F16DC018D28FD59@EX-DAG01.eckelmann.group> (raw)
Hi,
>
> On Tue, Feb 02, 2016 at 03:59:41PM +0100, Gavin Schenk wrote:
> > This is needed when using top in batch mode "top -b"
> > ---
> > rules/ncurses.make | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/rules/ncurses.make b/rules/ncurses.make index
> > 57e8199..521af77 100644
> > --- a/rules/ncurses.make
> > +++ b/rules/ncurses.make
> > @@ -212,6 +212,7 @@ ifdef PTXCONF_NCURSES_TERMCAP
> > @$(call install_copy, ncurses, 0, 0, 0644, -,
> /usr/share/terminfo/l/linux, n);
> > @$(call install_copy, ncurses, 0, 0, 0644, -,
> /usr/share/terminfo/s/screen, n);
> > @$(call install_copy, ncurses, 0, 0, 0644, -,
> > /usr/share/terminfo/s/screen-256color, n);
> > + @$(call install_link, ncurses, /usr/share/terminfo/a/ansi,
> > +/usr/share/terminfo/d/dumb);
>
> Why the symlink and not the real /usr/share/terminfo/d/dumb?
>
Mostly because of my ignorance :). I have changed the patch and tested it, it works!
I will post the patch again.
Regards
Gavin
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next reply other threads:[~2016-02-08 7:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-08 7:05 Schenk, Gavin [this message]
[not found] <Re: [ptxdist] [PATCH] ncurses: Added /usr/share/terminfo/d/dumb to PTXCONF_NCURSES_TERMCAP>
2016-02-08 7:07 ` Gavin Schenk
-- strict thread matches above, loose matches on Subject: below --
2016-02-02 14:59 Gavin Schenk
2016-02-05 16:10 ` Michael Olbrich
2016-02-11 11:31 ` Michael Olbrich
2016-02-11 11:34 ` Michael Olbrich
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=D415CD2EC4182C4EAB90A76B7D9F16DC018D28FD59@EX-DAG01.eckelmann.group \
--to=g.schenk@eckelmann.de \
--cc=ptxdist@pengutronix.de \
/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