[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: Ingo Weinhold <ingo_weinhold@xxxxxx>
  • To: haiku-commits@xxxxxxxxxxxxx
  • Date: Tue, 14 May 2013 15:00:06 +0200

On 05/07/2013 09:37 AM, Stephan Aßmus wrote:

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

   * 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.
Yeah, one could add more GUI, namely a list of removed types and an "Unremove" button, but that sounds kind of silly.
Another case that needs special handling, is when there is a global entry and the user has made modifications, thus cloning the entry. The "Remove" button should better be called something like "Reset to default" in this situation.
Anyway, it's a low priority issue, so I won't invest any time in it any time soon. It will probably wait until after merging the PM branch into master.
On a related note, any opposition to creating a "R1/Package Management" version in Trac to track issues such as this one? Or rather a milestone or just a keyword? 

CU, Ingo

Other related posts:

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