Bug 30417

Summary: [PATCH] arla port installs possibly conflicting libutil.a and header files
Product: Ports & Packages Reporter: sit <sit>
Component: Individual Port(s)Assignee: assar <assar>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Latest   
Hardware: Any   
OS: Any   
Attachments:
Description Flags
file.diff none

Description sit 2001-09-07 15:40:00 UTC 
	arla installs list.h, heap,h and other such includes in /usr/local/include
	as well as /usr/local/lib/libutil.a. This causes a conflict in compiling
	SFS (for example) which links with /usr/lib/libutil.a.

Fix: The NetBSD port includes a patch to avoid installing these files:

	http://cvsweb.netbsd.org/bsdweb.cgi/pkgsrc/net/arla/patches/patch-ae

$NetBSD: patch-ae,v 1.3 2001/08/09 13:48:59 wennmach Exp $

Do not install libutil.a and the header files bool.h, hash.h, heap.h, list.h,
and log.h, nor any of the man pages. There is a potential conflict with other
libutils.
How-To-Repeat: 	1. Try to compile something that uses -I/usr/local/include but wants a
	   list.h that is later in its include path.
	2. Try to link something that requires something in /usr/lib/libutil.a
	   (e.g. openpty) but also has -L/usr/local/lib.
Comment 1 Peter Pentchev freebsd_committer freebsd_triage 2001-09-07 15:44:56 UTC 
Responsible Changed
From-To: freebsd-ports->assar

Over to maintainer; the enclosed patch looks reasonable.
Comment 2 assar freebsd_committer freebsd_triage 2001-09-08 18:02:34 UTC 
State Changed
From-To: open->closed

thanks for the bug report. 
a similar patch to the one supplied has been applied.
Comment 3 sit 2001-09-27 16:14:00 UTC 
While the patch did fix the problem of installing include files
from the util/ directory, it still installs other include files
(such as those in lib/roken).  base64.h conflicts with the base64.h
that the mozilla port needs to build.

Thus, the installation of include files in top-level /usr/local/include
is still a problem.

A more general solution is needed, e.g.:

* Do not install any header files; Debian's packages typically
  include a runtime package and a developer package.
* Install header files in an arla/ subtree. Since no one else
  will be including arla/foo.h, the package can install whatever
  it wants without fear of conflict.