Debian bug report logs - #1341
ncurses man pages confusing regarding #include files

Message received at debian-bugs:

From mdd.comm.mot.com!mitchell Sat Sep  9 11:30:00 1995
Return-Path: <mitchell@mdd.comm.mot.com>
Received: from pixar.com by mongo.pixar.com with smtp
	(Smail3.1.28.1 #15) id m0srUfA-0002DBC; Sat, 9 Sep 95 11:30 PDT
Received: from motgate.mot.com by pixar.com with SMTP id AA17635
  (5.67b/IDA-1.5 for debian-bugs-pipe@mongo.pixar.com); Sat, 9 Sep 1995 11:29:46 -0700
Received: from pobox.mot.com (pobox.mot.com [129.188.137.100]) by motgate.mot.com (8.6.11/8.6.10/MOT-3.8) with ESMTP id NAA26015 for <debian-bugs@pixar.com>; Sat, 9 Sep 1995 13:29:57 -0500
Received: from mdd.comm.mot.com (mdisea.mdd.comm.mot.com [138.242.64.201]) by pobox.mot.com (8.6.11/8.6.10/MOT-3.8) with SMTP id NAA03010 for <debian-bugs@pixar.com>; Sat, 9 Sep 1995 13:29:56 -0500
Received: from bb29c.mdd.comm.mot.com by mdd.comm.mot.com (4.1/SMI-4.1)
	id AA19906; Sat, 9 Sep 95 11:29:54 PDT
Received: by bb29c.mdd.comm.mot.com (4.1/SMI-4.1)
	id AA14548; Sat, 9 Sep 95 11:29:53 PDT
Date: Sat, 9 Sep 1995 11:29:52 -0700 (PDT)
From: Bill Mitchell <mitchell@mdd.comm.mot.com>
X-Sender: mitchell@bb29c
To: debian-bugs@pixar.com
Subject: ncurses man pages confusing regarding #include files
In-Reply-To: <Pine.SUN.3.91.950909102846.14470A-100000@bb29c>
Message-Id: <Pine.SUN.3.91.950909111203.14530A-100000@bb29c>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


PACKAGE:  ncurses
VERSION:  1.9.3

It seems that include files mentioned on ncurses man pages
e.g. #include <term.h> need to be included as
e.g. #include <ncurses/term.h>.

I gather that this is to allow both curses (from libc) and
ncurses to be installed alongside one another.

It seems that this will break some (perhaps all) source packages
(and debian-user-written sources as well) which use ncurses in
0.93r{5|6} once ncurses replaces curses after the move to elf.

If there's a good workaround which will prevent this breakage,
it needs to be made very visible to both debian package and
debian-user developers.

If the breakage is unavoidable, this needs to be made similarly
visible.

Or am I missing something which should be obvious to me?