All of lore.kernel.org
 help / color / mirror / Atom feed
From: justin <jlec@gentoo.org>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] Use config scripts to detect ncurses libs for menuconfig
Date: Thu, 28 Feb 2013 10:35:08 +0100	[thread overview]
Message-ID: <512F24CC.2090906@gentoo.org> (raw)
In-Reply-To: <201302271937.49565.yann.morin.1998@free.fr>

[-- Attachment #1: Type: text/plain, Size: 564 bytes --]

Hello,

> On a side note: is the old code still useful, now we use the config
> scripts? In other words: are there cases where a ncurses install would
> not provide those scripts?
> 
> If the answer is 'no', then just trash the old code away.
> 
> I've just tested Debian Squeeze (stable for now), and Cygwin, and they
> both do provide ncurses{,w}5-config.
> 

I looked into the ncurses releases back to 5.0. The first release
containing is version 5.6 released in 2006. So I would guess we can
assume that every system will have it.


justin


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]

  reply	other threads:[~2013-02-28  9:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-27 18:07 [PATCH 1/2] Use config scripts to detect ncurses libs for menuconfig jlec
2013-02-27 18:07 ` [PATCH 2/2] Use config scripts to detect ncurses libs for nconfig jlec
2013-02-27 19:02   ` Yann E. MORIN
2013-02-28  9:48     ` justin
2013-02-28 17:58       ` Yann E. MORIN
2013-02-27 18:37 ` [PATCH 1/2] Use config scripts to detect ncurses libs for menuconfig Yann E. MORIN
2013-02-28  9:35   ` justin [this message]
2013-02-28 18:08     ` Yann E. MORIN
2013-02-28 21:31       ` justin
2013-02-28 21:35         ` Yann E. MORIN
2013-02-28 21:38           ` justin

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=512F24CC.2090906@gentoo.org \
    --to=jlec@gentoo.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yann.morin.1998@free.fr \
    /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.