xfconf.eclass supports XFCONF as an array, but has no support for it as an variable. this is by design. the eclass-manpages lacks support for describing this, I propose to clone the code of @ECLASS-VARIABLE to @ECLASS-ARRAY to create a proper manpage.
an array is a variable. i'm guessing you mean scalar vs array. you could make this clearer by simply mentioning it in the @DESCRIPTION. i dont think a new tag is necessary to convey information to people. also, i'm guessing the reason you picked an array over a scalar was to handle whitespace correctly ... but your usage of the array in the src_configure is wrong which makes it kind of pointless. you need to be doing `econf "${XFCONF[@]}"` so that the args are expanded correctly. if you want to sanity check people, it's fairly easy to add to your eclass: if [[ ${XFCONF+set} == "set" ]] && [[ $(typeset -p XFCONF) != "declare -a XFCONF="* ]] ; then die "XFCONF needs to be an array, not a scalar" fi
(In reply to comment #1) > an array is a variable. i'm guessing you mean scalar vs array. > > you could make this clearer by simply mentioning it in the @DESCRIPTION. i > dont think a new tag is necessary to convey information to people. Fair enough, done > also, i'm guessing the reason you picked an array over a scalar was to handle > whitespace correctly ... but your usage of the array in the src_configure is > wrong which makes it kind of pointless. you need to be doing `econf > "${XFCONF[@]}"` so that the args are expanded correctly. Yeah, fixed, thanks > > if you want to sanity check people, it's fairly easy to add to your eclass: > if [[ ${XFCONF+set} == "set" ]] && [[ $(typeset -p XFCONF) != "declare -a > XFCONF="* ]] ; then > die "XFCONF needs to be an array, not a scalar" > fi Nice one, but I don't think we really need that. Thanks anyway Closing, nothing really left to do here
