Subject: pkg/12784: SDL and NAS?
To: None <gnats-bugs@gnats.netbsd.org>
From: None <nocturne@arepa.com>
List: netbsd-bugs
Date: 04/29/2001 11:41:08
>Number:         12784
>Category:       pkg
>Synopsis:       should devel/SDL depend on NAS?
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    pkg-manager
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun Apr 29 08:41:01 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     Eric Mumpower
>Release:        NetBSD stock 1.5, pkgsrc as of today <NetBSD-current source date>
>Organization:
Into Networks
	
>Environment:
	
System: NetBSD floyd.arepa.com 1.5 NetBSD 1.5 (GENERIC) #1: Sun Nov 19 21:42:11 MET 2000     fvdl@sushi:/work/trees/netbsd-1-5/sys/arch/i386/compile/GENERIC i386

>Description:

Depending on whether NAS (audio/nas) is already installed, SDL
(devel/SDL) will configure with or without support for NAS. As this
seems like a large subsystem, it seems inappropriate to have such
unpredictability in the build. (Unpredictable to someone who has not
noticed this behavior, that is.)

I'd argue to either always disable NAS support (if it's not needed by
most users) or to turn its usage into a mk.conf variable.

>How-To-Repeat:

pkg_delete nas; build SDL. Note that it configures without NAS support.
Reinstall audio/nas package; build SDL. Note that it configures with
NAS support. ("checking for NAS audio support... yes")
>Fix:

Either just add --disable-nas to the configure invocation, or add that
with a mk.conf variable which will re-enable nas and add it as a
dependency of SDL.
>Release-Note:
>Audit-Trail:
>Unformatted: