Re: Netatalk 4.x

2025-02-12 Thread blake
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} > > That's the default so you should omit

Re: Netatalk 4.x

2025-02-11 Thread Ryan Carsten Schmidt
On Feb 11, 2025, at 20:19, Blake wrote: > > startupitem.name${name} That's the default so you should omit this line. > startupitem.executable "${prefix}/sbin/netatalk -d -F ${prefix}/etc/afp.conf" Per guide.macports.org: Do not wrap values in quotes if passing arguments to the daemon; “ex

Re: Netatalk 4.x

2025-02-11 Thread blake
I have made some good progress on this port. However, the startup item functionality in the profile is giving me some difficulty. What I have in the ports is… startupitem.create yes startupitem.name${name} startupitem.executable "${prefix}/sbin/netatalk -d -F ${prefix}/etc/afp.conf" start

Re: Netatalk 4.x

2025-01-22 Thread Joshua Root
On 22/1/2025 16:29, Jason Liu wrote: Install count looks super low however. Yet one more example of why we should be encouraging as many MacPorts users as possible to be installing the 'mpstats' port, so that we can obtain better statistics. It will still be a self-selected sample, with

Re: Netatalk 4.x

2025-01-22 Thread Sergey Fedorov
Netatalk can be a shim to pick this or that version, and then having several versions in parallel does not create a confusion. On Jan 22, 2025 at 11:35 +0800, bl...@netjibbing.com, wrote: > OK thanks for that info. With Netatalk, it shows as building and running back > to Snow leopard i386 now. W

Re: Netatalk 4.x

2025-01-21 Thread Ryan Carsten Schmidt
On Jan 21, 2025, at 23:30, Jason Liu wrote: > > but I also don't remember how difficult it would be to turn a completely > separate port into a subport of another later on. Subports are merely a convenience for the programmer; there is no difference for the end user. If it is easier for the pro

Re: Netatalk 4.x

2025-01-21 Thread Jason Liu
> > What if I make a netatalk4 port and give that some time to bake before > making changes to the netatalk port to select the newer version based on OS? Off the top of my head, I can't think of any reason why that would be a problem, but I also don't remember how difficult it would be to turn a

Re: Netatalk 4.x

2025-01-21 Thread blake
OK thanks for that info. With Netatalk, it shows as building and running back to Snow leopard i386 now. What if I make a netatalk4 port and give that some time to bake before making changes to the netatalk port to select the newer version based on OS? Install count looks super low however. I 100

Re: Netatalk 4.x

2025-01-21 Thread Jason Liu
Take a look at the Portfile for MoltenVK: https://github.com/macports/macports-ports/blob/master/graphics/MoltenVK/Portfile The base MoltenVK port, which is just a stub, will select the correct versioned subport based on the user's macOS version. Unfortunately, there is no way to know how to divi

Re: Netatalk 4.x

2025-01-21 Thread Blake Garner
I like that idea. Is there a good example port that already does this? My plan is to get a functional PR started and hope for some collaborative advice.  I’m not very interested in spending a lot of effort testing every possible version of macOS. Can these supports have their own supported macOS ve

Re: Netatalk 4.x

2025-01-20 Thread Sergey Fedorov
Yeah, this is a better idea, perhaps. On Tue, Jan 21, 2025 at 10:13 AM Jason Liu wrote: > Whoever updates the Portfile, can you make sure to preserve the old > version(s) of netatalk using a versioned subport, i.e. 'netatalk3', > 'netatalk2' (or whatever), so that old versions of macOS can still

Re: Netatalk 4.x

2025-01-20 Thread Jason Liu
Whoever updates the Portfile, can you make sure to preserve the old version(s) of netatalk using a versioned subport, i.e. 'netatalk3', 'netatalk2' (or whatever), so that old versions of macOS can still use the older netatalk packages? I think that the 'netatalk' port should be whatever is the late

Re: Netatalk 4.x

2025-01-20 Thread Sergey Fedorov
I had a port for netatalk 3 somewhere; as I recall, it needed some fixes for the build. That was a while ago, I do not know what is the current status. Very much likely that netatalk 4 will be broken on older systems and possibly less useful than earlier versions. So yeah, I think it should be a se

Netatalk 4.x

2025-01-20 Thread blake
The Netatalk package has seen some serious updates recently with a new team working on it. I have made a couple efforts and getting a working port for the 4.x versions but meson build system is tripping me up. Also looking at compatbility it seems like we would want a netatalk4 package vs just u