Re: BLAS in pkgsrc: present and future

[Greg Troxel <gdt%lexort.com@localhost>]

> That behavior would go against the meaning of "preferred" though,
> making the variable name misleading.?? I think we would need to change
> the name to something like PKGSRC_BLAS_USER_ACCEPTED and perhaps also
> change PKGSRC_BLAS_ACCEPTED to PKGSRC_BLAS_PKG_ACCEPTED.??
> PKGSRC_BLAS_USER_ACCEPTED in this scenario could replace
> PKGSRC_BLAS_TYPE/PKGSRC_BLAS_EXCLUSIVE.

But, user-settable PREFERRED and package-settable ACCEPTED is
longstanding.  I think as long as it is docuemnted, then there is no
problem with PREFERRED being exclusive.  How many people are going to be
how confused, vs the people that would misread things that don't use the
pkgsrc-normal meanings?


> In summary:
>
> PKGSRC_BLAS_USER_ACCEPTED: List of implementations acceptable to user
> (mk.conf)

I really don't like using ACCEPTED in a user-settable variable.  I think
that 99% we just don't.

> PKGSRC_BLAS_PKG_ACCEPTED: List of implementations acceptable to
> package (package Makefile)
> _PKGSRC_BLAS_SELECTED: Internal, first match from lists above and must
> be present in both or build will fail