netatalk4 build lacks "ea" support

[Louis Guillaume <louis%zabrico.com@localhost>]

I'm using NetBSD-10 (recent build) and pkgsrc-2025Q3.

This is in mk.conf ...

PKG_OPTIONS.netatalk += kerberos pam dnssd

... and the result ...

# make show-options
Any of the following general options may be selected:
        appletalk
        debug    Enable debugging facilities in the package.
        dnssd    Enable DNS Service Discovery Protocol support.
        kerberos         Enable Kerberos support.
        ldap     Enable LDAP support.
        pam      Enable PAM support.

These options are enabled by default:
        appletalk dnssd pam

These options are currently enabled:
        appletalk dnssd kerberos pam

You can select which build options to use by setting PKG_DEFAULT_OPTIONS
or PKG_OPTIONS.netatalk.

... Also ...

# netatalk -V
netatalk 4.3.0 - Netatalk AFP server service controller daemon

This program is free software; you can redistribute it and/or modify it 
under
the terms of the GNU General Public License as published by the Free 
Software
Foundation; either version 2 of the License, or (at your option) any later
version. Please see the file COPYING for further information and details.

netatalk has been compiled with support for these features:

      Zeroconf support:	mDNSResponder
     Spotlight support:	No

              afp.conf:	/etc/netatalk/afp.conf
                  afpd:	/usr/pkg/sbin/afpd
            cnid_metad:	/usr/pkg/sbin/cnid_metad
    netatalk lock file:	/var/run/netatalk.pid



But no mention of "extended attributes".

I don't see any options for netatalk4 that enable the extended 
attributes support.

pkg_info -B does not show any indication. I guess the package uses 
"meson" to do the building, and I'm completely unfamiliar with that.

The pkgsrc Makefile has this:

PLIST_VARS+=            ea
.if ${OPSYS} == "SunOS" || ${OPSYS} == "DragonFly" || ${OPSYS} == 
"Linux" || \
        (${OPSYS} == "NetBSD" && ${OPSYS_VERSION} >= 070000) || \
        ${OPSYS} == "FreeBSD"
PLIST.ea=               yes
.endif


But I'm really unsure of what that PLIST is. I'm guessing it's an input 
to "meson" to build the configuration for compiling. But it doesn't work?

Any help getting xattrs/ea support going would be great.

--
Louis