>Number:         16354
>Category:       pkg
>Synopsis:       bulidlink.mk of aalib and aalib-x11 conflicts
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    pkg-manager
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun Apr 14 13:12:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Bernd Ernesti
>Release:        NetBSD 1.5ZC 14-April-2002
>Organization:
	
>Environment:
System: NetBSD
Architecture: i386
Machine: i386
>Description:
	I currently have a aalib-x11 installed on my system, because mplayer
	wants it.
	Now I am trying to install gphoto2, which now wants aalib.
	And here is the problem, both aalib and aalib-x11 have a CONFLICTS
	line for the other package.

	Normaly that wouldn't be a problem if thats a DEPENDS line in the
	gphoto2 package, but it is an buildlink.mk include and there seems
	to be no good way to fix this problem.

	The main difference between these two aallib packages is the
	'CONFIGURE_ARGS+= --with-x11-driver=no' in the aalib Makefile.

	I can see why gphoto2 use aalib, there is no need for X11 support since
	gphoto2 has no x11 interface, if you want one you have to use gtkam.

	But gtkam use the gphoto2 buildlink file and therefor only gets the
	aalib dependecy, and I don't know if thats enough for gtkam.
	I changed my local gphoto2 Makefile to use aalib-x11 instead of aalib
	to get it working for now on.
>How-To-Repeat:
	Install mplayer and then try to install gphoto2.
>Fix:
	It was suggested to me to change the dependencies from:

DEPENDS+=       aalib-[0-9]*:../../graphics/aalib

	to

DEPENDS+=       aalib{,-x11}-[0-9]*:../../graphics/aalib-x11

	But this will result in a problem with binary packages.

	aalib and aalib-x11 install the same files, thats why
	the are conflicting.
>Release-Note:
>Audit-Trail:
>Unformatted: