Re: pkg/43480: audio/SDL_mixer's optional dependencies should be PKG_OPTIONs

[Peter Bex <Peter.Bex%xs4all.nl@localhost>]

The following reply was made to PR pkg/43480; it has been noted by GNATS.

From: Peter Bex <Peter.Bex%xs4all.nl@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: 
Subject: Re: pkg/43480: audio/SDL_mixer's optional dependencies should be 
PKG_OPTIONs
Date: Sun, 20 Jun 2010 13:24:19 +0200

 On Sun, Jun 20, 2010 at 11:10:09AM +0000, Thomas Klausner wrote:
 >  I like the idea.
 >  We should have a standard way to let a package specify it needs
 >  SDL_mixer built e.g. with the mp3 option on, though. Ideas for that?
 
 That sounds like a good idea; that problem had occurred to me before and
 initially I thought a user ought to know what he's doing when he
 overrides the PKG_SUGGESTED_OPTIONS for this package.
 
 It sounds like this ought to be a new infrastructure option;
 PKG_REQUIRED_OPTIONS.SDL_mixer perhaps?  The building package could set
 the options that it needs and if SDL_mixer isn't built yet it could
 override the options in such a way that it always includes the needed
 options.  This may result in very confusing behaviour if we aren't
 careful: users might set PKG_OPTIONS.SDL_mixer or perhaps
 PKG_DEFAULT_OPTIONS to get rid of an annoying package.  It would be
 quite unexpected if the required options could override that.
 
 Also, what happens when SDL_mixer is already installed?  AFAIK there's
 no way to determine what options were set for an installed package at
 the time it was built.  Maybe a MESSAGE to tell the user that if he
 doesn't hear sound he should rebuild SDL_mixer with the right options?
 
 Cheers,
 Peter