Intention of "headers-not-in-tirpc"?

[Thorsten Kukuk]

Hi,

one question:

in sunrpc/Makefile we have three variables for header files:

headers
headers-in-tirpc
headers-not-in-tirpc

What is the reason for the differentiation between this?

$(headers) is always installed, that's ok.
$(headers-in-tirpc) and $(headers-not-in-tirpc) are only installed,
if $(link-obsolete-rpc) is yes. I would have expected, that
$(headers-not-in-tirpc) will be installed if link-obsolete-rpc is no, too.

Is this a bug, that $(headers-not-in-tirpc) is not added? Or is this
differentiation obsolete? 

The reason is, that the headers-not-in-tirpc list is incorrect, and the
question is, what would be the correct fix?

Another problem is:
from resolv/Makefile:
ifeq (,$(filter sunrpc,$(subdirs)))
# The netdb.h we install does '#include <rpc/netdb.h>', so one must exist.
# If sunrpc/ is built in this configuration, it installs a real <rpc/netdb.h>.
# If that's not going to happen, install our dummy file.
headers += rpc/netdb.h
endif

The test does not seem to work, since sunrpc seems to be always
include sunrpc. But if not, installing an empty rpc/netdb.h is a bug,
this breaks existing code and prevents tirpc from installing an own
version.

  Thanks,
    Thorsten

-- 
Thorsten Kukuk, Senior Architect SLES & Common Code Base
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)