Mantis - roxfiler
Viewing Issue Advanced Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
4052 regular use minor always 2009-11-23 11:32 2014-03-24 00:49
Reporter: skayser Platform:  
Assigned To: maciej OS:  
Priority: normal OS Version:  
Status: resolved Product Version:  
Product Build: Resolution: suspended  
Projection: none      
ETA: none Fixed in Version:  
Summary: 0004052: Options -> Types -> "Edit MIME rules" can't be opened, 0install missing
Description: I am trying to adjust the applications which are used to open file types. Not sure whether "Edit MIME rules" is the right place to do so, but i noticed that it can't be opened. Once you click "Edit MIME rules" the following error message is displayed in a pop-up:

This program (http://rox.sourceforge.net/2005/interfaces/MIME-Editor) [^] cannot be run, as the 0launch command is not available. It can be downloaded from here:

http://0install.net/injector.html [^]
Steps To Reproduce:
Additional Information: # pkgparam CSWroxfiler VERSION
2.9,REV=2009.11.21
Relationships
Attached Files:
Issue History
Date Modified Username Field Change
2009-11-23 11:32 skayser New Issue
2009-11-23 13:53 maciej Note Added: 0007026
2009-12-08 20:19 maciej Note Added: 0007078
2009-12-08 20:19 maciej Status new => resolved
2009-12-08 20:19 maciej Resolution open => suspended
2009-12-08 20:19 maciej Assigned To => maciej
2014-03-24 00:49 maciej Note Added: 0010778

Notes
(0007026)
maciej   
2009-11-23 13:53   
I can reproduce this problem.

I used to edit this in a different way:

- Right click the file you want to open with a specific application
- Click the file's context menu
- Set Run Action
- Enter a shell command

I'm not sure about the MIME-Editor. Perhaps it's a separate application which needs to be downloaded from https://sourceforge.net/projects/rox/files/MIME-Editor/, [^] packaged separately and added as a dependency?
(0007078)
maciej   
2009-12-08 20:19   
Changing to suspended. Will reopen or close when MIME-Editor is packaged.
(0010778)
maciej   
2014-03-24 00:49   
There is no point in waiting for this bug to be fixed. If you want it fixed, you (yes, you the reader) need to fix it yourself. If you're not already a package maintainer at OpenCSW, you can look at the 35 minute long tutorial[1] to get started - then you can offer your patch to package maintainers. You can find OpenCSW people on the users mailing list[2] and on the #opencsw channel on IRC on Freenode[3].

[1] Packaging tutorial http://youtu.be/JWKCbPJSaxw [^]
[2] OpenCSW users mailing list https://lists.opencsw.org/mailman/listinfo/users [^]
[3] #opencsw on Freenode http://www.opencsw.org/support/irc-channel/ [^]