From: Guido S. <__g...@we...> - 2005-02-09 09:03:19
|
On Tue, 08 Feb 2005 13:12:58 +0000 "Stephen Watson" <sw...@ul...> wrote: > Guido Schimmels <__g...@we...> 09/Feb/2005 12:40:49 > >On Tue, 8 Feb 2005 09:09:39 +1100 > >Lucas Hazel <luc...@di...> wrote: > > > >> I'm not sure EA's should be a default behaviour. Not all systems > have > >> pyxattr installed or even support EA's. I might look into adding an > >> originating url tag at a later date. > > > >I've shown how you can avoid this dependency by calling the setfattr > command line tool. > >You can simply check if this command exists and fail silently if not. > I can't see any harm in this. > > You can have extended attributes, but not setfattr. Linux and Solaris > implement them differently, both in terms of library calls and commands. > I really should add a page to the wiki going through all this. So I'll add if sys.platform == 'linux2': for now, I guess. All the more reason to add EA support to ROX-Lib and handle the platform issues there, rather than dealing with them in the applications. In the meantime, does someone know the proper calls for BSD's and Solaris, HFS+? Now I have only this: if sys.platform == 'linux2': os.system('setfattr -n user.mime_type -v text/x-vcalendar -h "%s" 2>/dev/null' % uri) os.system('setfattr -n user.creator -v Contacts -h "%s" 2>/dev/null' % uri) Of course now I'd like to see user.creator in the filer's property box. Not very usefull now, of course, but... Now I'll go googling for user.mime_type and see if It says anything about other common EA's. ...back. The Mac Creator is a fourcc code. You need to register a creator code at Apple for your application. Hmm. Not worth copying. Other xattr EA's in use: user.charset user.mime_encoding user.url |