[haiku-commits] Re: BRANCH HaikuPM-github.package-management [59a653b] in src/data: mime_db/application beos_mime/application mime_db beos_mime mime_db/text

  • From: Stephan Aßmus <superstippi@xxxxxx>
  • To: haiku-commits@xxxxxxxxxxxxx
  • Date: Tue, 07 May 2013 09:37:17 +0200

On 07.05.2013 04:45, HaikuPM-github.package-management wrote:

59a653b: Support multiple MIME DB directories

   Each installation location (system, common, common/non-packaged,
   ~/config, ~/config/non-package) can now have a read-only data/mime_db
   directory. ~/config/settings/beos_mime is now named mime_db as well. The
   contents of all directories makes up the MIME DB. Entries in more
   specific locations shadow entries in more general locations. Only the
   directory in ~/config/settings is where the registrar writes changes to.

   The new layout allows packages to contribute entries to the MIME DB by
   simply providing the respective files in data/mime_db. Consequently the
   user settings directory is supposed to contain only the things the user
   has actually changed.

   Seems to work fine as far as tested. A few issues, though:

[...]


   * ATM it is not possible to remove a MIME type that is not in the user
     settings directory, although the FileTypes GUI suggests that it is.
     We'd have to work with white-outs, since we cannot remove the files in
     the data/mime_db directories. Or, alternatively, the API has to be
     extended and the FileTypes GUI adjusted to disable the "Remove" button
     in such a case.
I would be for disabling the Remove option. I think the biggest reason for having it in the first place was to be able to cleanup after deinstalling some apps maybe. But now that would automatically remove the mime-types already. Once some mime-type is hidden by a white-out, it sounds hard to get it back. I'd rather not go down that path. 

Best regards,
-Stephan

Other related posts:

  1. Home
  2. haiku-commits
  3. Archive
  4. 05-2013