Subject: Re: identify packages that were custom built?
To: Jeremy C. Reed <reed@reedmedia.net>
From: Dieter Baron <dillo@danbala.tuwien.ac.at>
List: tech-pkg
Date: 09/19/2007 18:34:34
In article <Pine.NEB.4.64.0709191056490.28954@glacier.reedmedia.net> Jeremy wrote:
: On Wed, 19 Sep 2007, Jeremy C. Reed wrote:

: > Maybe that could be set if PKG_SUGGESTED_OPTIONS doesn't match 
: > PKG_OPTIONS, but that may be hard if things are in different order.

  make can sort lists, so this should be rather easy.  I would,
however, not encode this into the binary package, but let the tool do
the test.  PKG_SUGGESTED_OPTIONS can be included in binary packages
(and pkg_summary) if you want.

: Or maybe check the variable defined by PKG_OPTIONS_VAR is 
: defined?

: Untested:

: .if defined(PKG_OPTIONS_VAR) && defined(${PKG_OPTIONS_VAR})
: CUSTOM=true
: BUILD_DEFS+=    CUSTOM
: .endif

  This does not take into account PKG_DEFAULT_OPTIONS, let alone
non-options variables that change the build.

:   Jeremy C. Reed