On Sat, 2012-08-25 at 23:45 +0200, Ulrich Mueller wrote:
> >>>>> On Sat, 25 Aug 2012, Alexandre Rostovtsev wrote:
>
> > export VALAC=$(type -P valac-${VALA_API_VERSION})
> > export VALA=$(type -P vala-${VALA_API_VERSION})
> > export VALA_GEN_INTROSPECT=$(type -P
> > vala-gen-introspect-${VALA_API_VERSION})
> > export VAPIGEN="$(type -P vapigen-${VALA_API_VERSION})"
>
> Is it guaranteed that these commands are present at pkg_setup time?
I am assuming that the ebuild writer has added the correct vala
dependency to DEPEND. Maybe something like this:
VALA_API_VERSION=0.16
DEPEND="vala? ( >=dev-lang/vala-0.16.1:${VALA_API_VERSION}[vapigen] )"
In which case, the vala commands that are pulled in via DEPEND will be
(unless I am completely wrong about how pkg_config works) available
during pkg_config.
Commands that are not pulled in via DEPEND of course might not be
available, in which case VALAC or VAPIGEN etc. would be set to the empty
string by vala_pkg_config.
For all vala-using build systems that I have seen, this should not break
anything.
However, for a cleaner and safer environment, I could do the following:
local path
path=$(type -P valac-${VALA_API_VERSION})
[[ -n "${path}" ]] && VALAC="${path}"
path=$(type -P vala-${VALA_API_VERSION})
[[ -n "${path}" ]] && VALA="${path}"
path=$(type -P vala-gen-introspect-${VALA_API_VERSION})
[[ -n "${path}" ]] && VALA_GEN_INTROSPECT="${path}"
path=$(type -P vapigen-${VALA_API_VERSION})
[[ -n "${path}" ]] && VAPIGEN="${path}"
