From: Stephen W. <wa...@ue...> - 2003-08-28 07:43:05
|
In message <200...@mo...> David Jeske <je...@ch...> scribbled: > On Wed, Aug 27, 2003 at 09:28:55PM +0200, Jaap Karssenberg wrote: > > On Wed, 27 Aug 2003 10:01:45 -0700 David Jeske wrote: > > : The purpose of a centralized mime-info database is different than > > : AppInfo mime-exports. As an application author, I don't want to have > > : to learn about all the different centralized mime-type databases (of > > : which there are several and always will be), I just care about one > > : thing --> distributing my application. If your system uses the > > : freedesktop shared mime-info database, great, you can build your > > : information from AppInfo.xml files. If my system uses Gnome, KDE, or > > : who knows what else, great, I can teach those systems to read from > > : AppInfo.xml files also. > > > > But the xml for the freedesktop database is almost identical to what you > > are proposing, only it would be a seperate file in your package instead > > of being in AppInfo - so why not adopt the freedesktop xml and learn > > Gnome and KDE that ? > > Sounds fine. When I look at the freedesktop site all I find is lots of > information about the centralized mimetype database. Can you tell me > where I can find this simple mimetype info file, and information > encouraging application authors to just passivly put it in a > relocatable package like AppInfo? For a concrete example look at how the filer installs a type definition for .DirIcon files. It copies rox.xml into ${SHAREDIR}/mime/packages and runs update-mime-database. Look at install.sh and rox.xml in the source distribution. This is covered in the Shared MIME-info Database spec. -- Stephen Watson Physicist Ultra Electronics Ltd - Signature Management Systems (UESMS) Tel: +44 (0)1543 878888 (switchboard) Fax: +44 (0)1543 878249 Email: wa...@ue... |