John W <jwdevel_at_gmail.com> wrote on
Date: Wed, 07 May 2025 23:05:42 UTC :
> . . .
>
> As far as I am able to tell, the behavior I described *is* a bug with that
> port.
The Makefile is correct for poudriere(-devel)
use. ${FLAVOR} in OPTIONS_FILE does expand to
the likes of py311 for that type of context.
Copying the text from my comment about the
Makefile operation (for building python
packages):
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=286659#c19
QUOTE
(In reply to jwdevel from comment #15)
Not a reopening, just a confirming of details
of the existing Makefile working for poudriere
operation . . .
I have confirmed what Muhammad reports. In
essence that use of:
poudriere options www/py-autobahn
does lead to there being a: (note the py311)
/usr/local/etc/poudriere.d/options/www_py-autobahn/py311-options
with the option that I set for the test
changed (COMPRESSION enabled):
# This file is auto-generated by 'make config'.
# Options for py311-autobahn-24.4.2_1
_OPTIONS_READ=py311-autobahn-24.4.2_1
_FILE_COMPLETE_OPTIONS_LIST=ACCELERATE COMPRESS ENCRYPTION SCRAM SERIALIZATION
TWISTED
OPTIONS_FILE_SET+=ACCELERATE
OPTIONS_FILE_SET+=COMPRESS
OPTIONS_FILE_SET+=ENCRYPTION
OPTIONS_FILE_SET+=SCRAM
OPTIONS_FILE_SET+=SERIALIZATION
OPTIONS_FILE_SET+=TWISTED
So the use of ${FLAVOR} in OPTIONS_FILE does work
for poudriere(-devel) use.
And, so, I learn something new to me about
FLAVOR usage for python builds. Sometimes
learning curves are messy. Sorry.
END QUOTE
Unfortunately, my lack of familiarity with the
use of ${FLAVOR} in places instead of use of
${PY_FLAVOR} for python package builds means
that I added to the mess for this bugzilla
submittal before I finally challenged the right
bad assumption that I had.
===
Mark Millard
marklmi at yahoo.com
