On Thu, Aug 21, 2003 at 10:20:37AM -0400, Todd Vierling wrote:
> On Thu, 21 Aug 2003, Sean Davis wrote:
> 
> : mplayer would be a good example. Unless you specifically disable arts in
> : mk.conf, you have to build KDE to build mplayer.
> 
> Well, not completely true; you need QT and ARTS.  KDE is not needed.  (Its
> buildlink2.mk is in arts/buildlink2.mk, but commented out....)

It is my understanding that ARTS needs KDE. If neither QT or ARTS need KDE,
then why does mplayer go off building kdebase unless you disable ARTS in
mk.conf?

> 
> But if you can turn it off in mk.conf, then there is no problem.  Binary
> packages meant for public distribution should be built with no options set
> and be fully functional; knobs to *turn off* some behaviors are acceptable
> on a per-person basis.

I suppose I agree, but it would be nice if it were easier to find the knobs
than to have to dig through bsd.pkg.mk. (as in, if there were an MKOPTIONS
file in the pkgsrc dirs, that listed the different options for that package.
I realize that would be a lot of work, its not really a suggestion, but it
would be nice.)

-Sean

-- 
/~\ The ASCII
\ / Ribbon Campaign                   Sean Davis
 X  Against HTML                       aka dive
/ \ Email!