[Bug 268893] Mk/Uses/python.mk: need a way to specify wheel name != PORTNAME

2023-01-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268893 Nuno Teixeira changed: What|Removed |Added Blocks||268902 Referenced Bugs: https://

[Bug 268893] Mk/Uses/python.mk: need a way to specify wheel name != PORTNAME

2023-01-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268893 --- Comment #7 from Nuno Teixeira --- (In reply to Yasuhiro Kimura from comment #5) audio/py-gtts: Update to 2.3.0, PR 268902 --- ===> Building for py39-gtts-2.3.0 Successfully built gTTS-2.3.0-py3-none-any.whl ===> Staging for py39-gt

[Bug 268893] Mk/Uses/python.mk: need a way to specify wheel name != PORTNAME

2023-01-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268893 --- Comment #8 from Nuno Teixeira --- (In reply to Nuno Teixeira from comment #7) (...) Simple solution is to rename PORTNAME from gtts to gTTS to build ok. -- You are receiving this mail because: You are on the CC list for the bug.

[Bug 268893] Mk/Uses/python.mk: need a way to specify wheel name != PORTNAME

2023-01-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268893 --- Comment #9 from Charlie Li --- Even though the wheel specification discourages it, since uppercase letters were supported in an earlier specification version, they will continue to be supported here. Thus PORTNAMEs will need to match th

[Bug 268893] Mk/Uses/python.mk: need a way to specify wheel name != PORTNAME

2023-01-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268893 --- Comment #10 from Nuno Teixeira --- (In reply to Charlie Li from comment #9) Is this a reason to start renaming ports or should we wait until a better option comes up? -- You are receiving this mail because: You are on the CC list for

[Bug 268893] Mk/Uses/python.mk: need a way to specify wheel name != PORTNAME

2023-01-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268893 --- Comment #11 from John Hein --- (In reply to Charlie Li from comment #9) The PORTNAME guidance on the wiki conflicts for cases like gTTS (MUST be lowercase and MUST match upstream) - see bug 268892. Should the 'lowercase' guidance just

[Bug 268893] Mk/Uses/python.mk: need a way to specify wheel name != PORTNAME

2023-01-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268893 Yasuhiro Kimura changed: What|Removed |Added Status|New |Open --- Comment #12 from Yasuhi

[Bug 268893] Mk/Uses/python.mk: need a way to specify wheel name != PORTNAME

2023-01-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268893 --- Comment #13 from Charlie Li --- (In reply to Yasuhiro Kimura from comment #12) These ones are compliant, with dashes/hyphens normalised to underscores for the built distributions (wheels). -- You are receiving this mail because: You a

[Bug 268893] Mk/Uses/python.mk: need a way to specify wheel name != PORTNAME

2023-01-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268893 --- Comment #14 from Charlie Li --- (In reply to John Hein from comment #11) Looking at the revision history, looks like an oversight when clarifying differing cases on whether the package is registered on PyPI or not. For packages with upp

[Bug 268893] Mk/Uses/python.mk: need a way to specify wheel name != PORTNAME

2023-01-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268893 --- Comment #15 from Yasuhiro Kimura --- (In reply to Charlie Li from comment #13) > These ones are compliant, with dashes/hyphens normalised to underscores for > the built distributions (wheels). Then it seems 'USE_PYTHON=pep517' doesn'

[Bug 268893] Mk/Uses/python.mk: need a way to specify wheel name != PORTNAME

2023-01-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268893 Charlie Li changed: What|Removed |Added Attachment #239409|0 |1 is obsolete|

[Bug 268893] Mk/Uses/python.mk: need a way to specify wheel name != PORTNAME

2023-01-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268893 --- Comment #17 from Charlie Li --- Comment on attachment 239433 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=239433 python.mk: normalise wheel filename arguments [0] https://packaging.python.org/en/latest/specifications/binar

[Bug 268893] Mk/Uses/python.mk: need a way to specify wheel name != PORTNAME

2023-01-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268893 --- Comment #18 from Yasuhiro Kimura --- (In reply to Charlie Li from comment #16) I applied attachment 239433 and staging failed with different error. yasu@rolling-vm-freebsd2[1034]% make stage ===> License APACHE20 GPLv2+ accepted by t

[Bug 268893] Mk/Uses/python.mk: need a way to specify wheel name != PORTNAME

2023-01-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268893 Charlie Li changed: What|Removed |Added Attachment #239433|0 |1 is obsolete|

[Bug 268893] Mk/Uses/python.mk: need a way to specify wheel name != PORTNAME

2023-01-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268893 --- Comment #20 from Yasuhiro Kimura --- (In reply to Charlie Li from comment #19) With attachment 239434 `make stage` finished successfully. But now `make check-plist` fails as following. > Checking for pkg-plist issues (check-plist)

[Bug 268893] Mk/Uses/python.mk: need a way to specify wheel name != PORTNAME

2023-01-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268893 --- Comment #21 from Charlie Li --- (In reply to Yasuhiro Kimura from comment #20) 'USE_PYTHON=autoplist pep517' works as intended, but currently does not handle data_files installation as setuptools deprecated this practice [0]. spf-engine

[Bug 268893] Mk/Uses/python.mk: need a way to specify wheel name != PORTNAME

2023-01-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268893 --- Comment #22 from Yasuhiro Kimura --- (In reply to Charlie Li from comment #21) Thanks for explanation. Then what is the best practice at the moment? Should I stop using 'USE_PYTHON=autoplist' and add pkg-plist? -- You are receiving t