Robert Elz <kre%munnari.OZ.AU@localhost> writes: > | - packets from pkgsrc (like samba) will continue to have the > | corresponding options disabled by default > > Those packages could have warnings in DESCR and MESSAGE (or whatever it > is called) advising of the need for FFSv2ea for full functionality. > How does samba (and anything else like it) deal with this - if it is > a compile time option, then since NetBSD supports EAs (and hence the > sys call interface exists) EA support in samba should be enabled. > More likely it is to be a run time problem, as whether a filesys has > EA support or not will vary, some might, others not, so whether samba > can provide EA functionality will tend to vary file by file (or at least > directory by directory) - given that, a solid warning that FFSv2ea support > is needed in the samba man page (or other doc) for NetBSD should allow > users to know what to do. Not MESSAGE; this is not a "your hair is on fire" thing. And it's not just NetBSD --- it's a larger issue that you need to use a FS with certain properties if you want certain features. So it really belongs in the upstream documentation in general. As a general point, these sorts of issues are not properly pkgsrc accomodations, but belong upstream, as anyone building samba from sources following the upstream build instructions should get the same hints. Indeed, a warning in the code (pushed to the upstream project) about using ACLs in a fs that doesn't have ACLs seems good.
Attachment:
signature.asc
Description: PGP signature