Re: easy way to know custom options were used?

["OBATA Akio" <obache%netbsd.org@localhost>]

On Fri, 25 Sep 2009 23:24:08 +0900, Jeremy C. Reed 
<reed%reedmedia.net@localhost> wrote:

> On Fri, 25 Sep 2009, Larson, Timothy E. wrote:
>
> > > _BUILD_DEFS+=      PKG_SUGGESTED_OPTIONS
> >
> > I think this is a fabulous idea.  Recording suggested and actual
> > options used at time of package creation could be very helpful.
>
> The reason I was looking at this is I want a package installation tool
> to warn if the PKG_OPTIONS doesn't match the PKG_SUGGESTED_OPTIONS of an
> existing installed package if requested to "update" it. In other words:
> warn if replacing a custom package. I can't be too specific since there
> is no easy way to know if the option names had changed and newer package
> may provide the same features even if options changed.
>
> I realize I had posted a similar email about this earlier this year too:
> http://mail-index.netbsd.org/tech-pkg/2009/02/25/msg002722.html

I may have a misunderstanding about your suggestion.

As the situation in the above mail,

Currentliy PKG_OPTIONS=#empty (-gnome),
  If try to install wihout -gnome, PKG_OPTIONS=gnome,             WARN.
  If try to install with -gnome, PKG_OPTIONS=#empty,              OK.
  If PKG_SUGGESTED_OPTIONS changed to empty, PKG_OPTIONS=#empty,  OK.
     try to install with gnome, PKG_OPTIONS=gnome,                WARN.

(I may want PKG_SUPPORTED_OPTIONS in BUILD_INFO.)

--
"Of course I love NetBSD":-)
OBATA Akio / obache%NetBSD.org@localhost