Re: Netatalk 4.x

The quoting on startupitem.executable was my main issue. I’ll incorporate these other tips as well. Thanks! > On Feb 11, 2025, at 9:30 PM, Ryan Carsten Schmidt > wrote: > > On Feb 11, 2025, at 20:19, Blake wrote: >> >> startupitem.name${name} > > Th

Re: Netatalk 4.x

d. Possibly PATH needs to be set, but I don’t see that option in port startupitem syntax. Suggestions for debugging? The software comes with a launchd plist that’s a little bare bones. I could edit/patch that for use. Write my own launchd plist without daemondo? Thanks, Blake > On Jan 22, 2

Re: Please do not remove Tiger support

It seems like the interested people fork MacPorts just before the commits that remove 10.4 and focus on supporting that for the legacy funtime use case. Let that fork of Macports age gracefully with the hardware that supports it. Reducing the burden of keeping current macports up to date and fun

Re: Recent events ...

I saw that the swift.org team has adopted https://www.contributor-covenant.org It could be an option. > On Feb 4, 2025, at 5:57 PM, Joshua Root wrote: > > On 5/2/2025 05:18, Nicklas Larsson via macports-dev wrote: >> I’m not aware o

Re: Netatalk 4.x

second method is often considered > to be a compelling reason why those of us MacPorts devs who are interested in > supporting older macOS versions will sometimes set up virtual machines for > each and every older macOS version. > > -- > Jason Liu > > > On Wed, Jan 22, 2

Re: Netatalk 4.x

fileThe meson build system only has one flag for the path to bdb for example. With include and lib needing to be specified for MacPorts compatibility, it seems like I would need to hack up the meson config to get the current version to build. For no I’m pointin to some local filesystem as a hack t

Netatalk 4.x

version to build. For no I’m pointin to some local filesystem as a hack to make it build. /Users/blake/scratch/netatalk/bdb/ ├── db48 -> /opt/local/lib/db48/ ├── include -> /opt/local/include/db48/ └── lib -> /opt/local/lib/db48/ There are also a bunch of other binaries that are part

Re: Requesting Ticket Closure for legacy libfido2 issues

Hey, Sergey, which tickets are you referring to? I think wontfix is appropriate here. I’m not easily finding the platforms option, but I’m happy to get that added. If somebody has an example or some reference for that? > On Jul 8, 2024, at 9:33 AM, Sergey Fedorov wrote: > > Perhaps actua

Requesting Ticket Closure for legacy libfido2 issues

I don’t have the ability to close tickets in trac for the libfido2 port, which I’m a maintainer of. Legacy support stuff... https://trac.macports.org/ticket/68333 https://trac.macports.org/ticket/64833 User CLT config issue… https://trac.macports.org/ticket/68486 Thanks, Blake

Re: Help getting new port nrsc5 working

Ok I’ll get it sorted. Thanks! > On Apr 16, 2023, at 9:37 PM, Joshua Root wrote: > > On 17/4/2023 09:01, bl...@netjibbing.com wrote: >> It looks like I had a previous partial install that was causing this error. >> I edited the CMakeLists.txt and got it to build, which in turn cleaned up >> th

Help getting new port nrsc5 working

laration is here int nrsc5_pipe_samples_cs16(nrsc5_t *st, int16_t *samples, unsigned int length); ^ 2 errors generated. make[2]: *** [src/CMakeFiles/nrsc5_object.dir/nrsc5.c.o] Error 1 Thanks, Blake

Re: OpenSSH 8.9p1 deprecated variants cleanup feedback request

Having also spent time with the OpenSSH port to add Fido support we should just drop the hard-to-maintain variants is my view. On Wed, Mar 16, 2022 at 3:54 PM Clemens Lang wrote: > On Mon, Mar 14, 2022 at 10:14:05PM +, grey wrote: > > What do others think? Feedback is welcome! I didn't mean

Re: Help offered (macOS VMs)

Is there a reason macports would not use VMware Fusion for x86 versions? It has the best macOS support and I'm sure that macports could get some licenses as needed for free. For PPC I have had good luck with qemu in the past. On Tue, Sep 7, 2021 at 1:41 AM Ruben Di Battista wrote: > I'm also ver

macmini colo m1

Hey I saw this offer of free access to m1 mini hardware from macmini colo for opensource projects. Not sure about who/what qualifies in regards to macports but figured I'd pass it along. https://www.macstadium.com/opensource Blake

Re: the whole world is renaming the git default branch to main...

Yep it’s time. Renaming the branch has been easy for the ones I have done. it’s the update of automation systems that is the work. On Sun, Mar 14, 2021 at 11:50 AM Blair Zajac wrote: > +1 for renaming. > > https://github.com/github/renaming > https://sfconservancy.org/news/2020/jun/23/gitbranchn

Re: Looking to resolve Qemu on AppleSilicon build failure

if it's a successful building with +vnc on the build bots? On Thu, Mar 4, 2021 at 1:30 AM Ryan Schmidt wrote: > > > On Mar 4, 2021, at 00:16, Blake Garner wrote: > > > Building with the vnc variant is failing for me at the configure step. I > was able to resolve a previous ld e

Re: Looking to resolve Qemu on AppleSilicon build failure

Build version 12D4e sudo port install qemu +cocoa +target_arm +usb +vnc https://gist.github.com/trodemaster/249f812e6b66275e5649b219dd8f92cc On Thu, Feb 18, 2021 at 12:03 PM Blake Garner wrote: > I was able to build qemu on my m1 mini with the port from the linked PR! > Should be able to

Re: Looking to resolve Qemu on AppleSilicon build failure

qemu port. Reverting to the Xcode cli tools 12.4 worked. Blake On Thu, Feb 18, 2021 at 10:14 AM Blake Garner wrote: > Thanks for closing the loop on that. I'll do some testing with that PR as > it includes the needed patches to support hypervisor.framework. > > Blake > > On

Re: Looking to resolve Qemu on AppleSilicon build failure

Thanks for closing the loop on that. I'll do some testing with that PR as it includes the needed patches to support hypervisor.framework. Blake On Thu, Feb 18, 2021 at 9:36 AM Rainer Müller wrote: > On 18/02/2021 05.23, Joshua Root wrote: > > On 2021-2-18 08:33 , Blake Garner

Looking to resolve Qemu on AppleSilicon build failure

configure scripts to isolate differences between the working and not working builds? Thanks, Blake

Re: "cask" ports just keep on rolling in...

I also think this would be highly desirable. Would it be another portgroup that needs to be written in tcl? On Fri, Feb 5, 2021 at 11:01 AM Ken Cunningham < ken.cunningham.web...@gmail.com> wrote: > With no plan, we’ll just keep getting more and more of these. > >

Re: Updating OpenSSH port to 8.4p1

Thanks will do. On Sat, Oct 17, 2020 at 12:24 AM Nils Breunese wrote: > Blake Garner wrote: > > > Successfully rolled the version of openssh to 8.4p1 and incremented the > port revision to 10. > > I see the Portfile Reference [0] doesn’t mention this, but when you > in

Re: Updating OpenSSH port to 8.4p1

keep at it as I find time. Blake On Thu, Oct 1, 2020 at 12:18 AM Mojca Miklavec wrote: > Dear Blake, > > On Wed, 30 Sep 2020 at 19:56, Blake Garner wrote: > > > > I see that the port for OpenSSH has no maintainer and hasn't been > updated in a while. Reviewing the do

Updating OpenSSH port to 8.4p1

I see that the port for OpenSSH has no maintainer and hasn't been updated in a while. Reviewing the docs it looks reasonable for me to try and update the port and submit it. Is anybody else already working on it? Advice for a updating a port the first time beyond what's on the site? Thanks, Blake