pre-build packages for Lion
What are the intervals that pre-build packages for Lion are generated? For example, `libpaper` is already available, but `ghostscript` is not, and neither is 'texlive-bin'... And while we are at it, 'ports.macports.org' reports that 'lilypond' can't be build on Lion due to ``` Dependency 'poppler' with variants '+boost' has previously failed and is required. ``` (why is `+boost` needed?) However, looking into the 'poppler' page on 'ports.macports.org' it seems that the Lion build is healthy – and the variant '+boost' has been just built from source on my computer without a problem... Werner
Re: Portfile magic / xinstall usage / defect?
(Moving to macports-dev) Frank Stock wrote: My main focus is .pkg component installers targeting systems where a development toolchain is not realistic. * Do you think it would be possible to use mtree and add_users data to generate code for a postinstall script handling user/group creation and file ownership? * If so, would there be any interest from the MacPorts team in a pull request for that? So it sounds like you're saying that file ownership is not currently preserved by 'port pkg'? :) Yes, a reasonable PR to fix that would most likely be accepted. However I don't think a postinstall script would be required, I'm pretty sure it would just be a config option for pkgbuild or something. - Josh
NCDU Fails b/c Zig
I have a M3 iMac and wondering if there was a workaround on fixing Zig so I can install ncdu? main.log Description: Binary data
Re: Portfile magic / xinstall usage / defect?
Thanks for that link Josh.
I did not realize that MacPorts was building an internal mtree.
My main focus is .pkg component installers targeting systems where a
development toolchain is not realistic.
* Do you think it would be possible to use mtree and add_users data to generate
code for a postinstall script handling user/group creation and file ownership?
* If so, would there be any interest from the MacPorts team in a pull request
for that?
-Frank
Since I have the automation, I am able to address
> On Dec 8, 2023, at 9:17 PM, Joshua Root wrote:
>
>> The brotli
>> Portfile:https://github.com/macports/macports-ports/blob/master/archivers/brotli/Portfile
>> Contains:
>> post-destroot {
>> xinstall -m 640 {*}[glob ${worksrcpath}/docs/*.1]
>> ${destroot}${prefix}/share/man/man1/
>> …
>> }
>>
>> However, after port installation, I look in the work directory and see:
>> ls -la destroot/opt/local/share/man/man1
>> -r--r--r-- root admin … brotli.1.gz
>>
>> Also, /opt/local/share/man/man1/brotli.1.gz contains the same perms and .ext
>> (as the above work/destroot).
>>
>> * How is the permissions mode 444, instead of 640 (as designated in the
>> post-destroot block)?
>> * And how did it get the .gz extension?
>
> If you look in the log file for the brotli build after running e.g. 'sudo
> port destroot brotli', you'll see a line saying "Compressing man pages for
> brotli". That comes from this code (which runs after all Portfile-defined
> destroot code):
>
>
> - Josh
>
Re: anyone use OpenVPN or WireGuard on OS X 10.9.5?
On Saturday December 09 2023 12:26:05 Steven Smith wrote: >Yes, I used OpenVPN. For a decent configuration, see: After trying several GUI wrappers in their legacy version for 10.9 which all failed with similar errors I discovered that OpenVPN2 can take the configuration files that you can download from ProtonVPN after setting up an account (even a free one). It does need the kext installed through port:tuntaposx and you need to execute the command as root. That's probably where the convenience wrappers fail. >I rely on Tunnelblick to manage the connection. I’ve tried to migrate the >Tunnelblick build to MacPorts, without any success: The currently available sources require a pretty new OS version to build, IIRC. R.
