Benjamin Peterson <benja...@python.org> added the comment: 2012/3/12 Nicholas Riley <rep...@bugs.python.org>: > > Nicholas Riley <com-python-b...@sabi.net> added the comment: > > I've spent a few hours looking at xattr and the Linux/OS X (10.4+) > implementations. Bob Ippolito's xattr module implements the OS X xattr > interface on Linux, Solaris (9+) and FreeBSD. Linux and OS X are pretty > close; FreeBSD and Solaris are substantially different from either and the > Solaris implementation is somewhat incomplete/broken. > > The OS X differences from Linux are: > > • Instead of l* functions, the XATTR_NOFOLLOW option > > • XATTR_NOSECURITY and XATTR_NODEFAULT are in the headers but essentially > unavailable as the kernel code always returns EINVAL for them. > > • XATTR_SHOWCOMPRESSION to expose the HFS compression stuff, which I can't > imagine many people needing > > • XATTR_MAXNAMELEN (but no equivalent to XATTR_SIZE_MAX). Linux has a > corresponding XATTR_NAME_MAX, which we should probably expose too. > > • XATTR_FINDERINFO_NAME and XATTR_RESOURCEFORK_NAME for some standard > attribute names. I would imagine these are worth exposing. > > I don't see any problems supporting the currently exposed Linux API on OS X > (I could probably find a usable value for XATTR_SIZE_MAX), but it's unclear > if that is the right way to go forward. > > Suggestions?
Thanks for looking into this. I think the best approach at the moment is try to wrap these differences under the LInux API. It seems the biggest one will just be adding XATTR_NOFOLLOW for the l* calls. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue12978> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
