On 2022-3-22 12:20 , Ryan Schmidt wrote:
It is not even our policy that contributors must read the NEWS or CHANGELOG
files to see what changed, though I sometimes do this as it helps me discover
things like if dependencies need to be changed.
It may not be required by policy, but I would cons
Sorry, this got long.
I want to move a discussion to the macports-dev list that began with a user's
question to macports-mgr. This user ran a third-party utility which reported
that some files installed by MacPorts were not codesigned and asked if it was a
concern.
I replied that the files ins
Thanks. I’ll try if I can to your latter suggestion later, the portfile also
uses this line with ${python.version} so it might not be that easy.
Zhenfu
> On Mar 21, 2022, at 16:13, Joshua Root wrote:
>
> On 2022-3-22 06:51 , Zhenfu Shi wrote:
>> Hi all,
>> I’m trying to add Python 3.10 variant
On 2022-3-22 06:51 , Zhenfu Shi wrote:
Hi all,
I’m trying to add Python 3.10 variant to a few ports, but one of them (mpv) uses
`set python_branch [join [split ${ver} {}] ".”]` to convert branch strings to
version strings, resulting in “310” being converted to “3.1.0”. Can anyone advise
how t
Hi all,
I’m trying to add Python 3.10 variant to a few ports, but one of them (mpv)
uses `set python_branch [join [split ${ver} {}] ".”]` to convert branch strings
to version strings, resulting in “310” being converted to “3.1.0”. Can anyone
advise how to change this line so it gives “3.10” wit
