Re: Bug#195214: .iso conflict, discussion of resolution
On Sat, Aug 30, 2003 at 08:06:18PM -0500, Chris Cheney wrote: > On Sat, Aug 30, 2003 at 06:08:17PM -0400, Matt Zimmerman wrote: > > On Fri, Aug 29, 2003 at 10:34:39PM -0700, Mike Markley wrote: > > > > > A quick summary of this bug: > > > Arson, a KDE CD burning application, includes two .desktop files to > > > associate certain files with it: > > > /usr/share/mimelnk/application/x-iso.desktop > > > /usr/share/mimelnk/application/x-cue.desktop > > > > And presumably another application also wants to include these files? Is > > KDE's file association system really so broken that two programs cannot both > > declare themselves able to handle a certain type of file? > > Nope, mime types are completely independent of them declaring if they > support it. That is why the mimetype really belongs in kdelibs itself > and not the 3rd party package. Ah, so these files are to define a MIME type, and not to associate files (as they were described above). That makes more sense. -- - mdz
Re: Bug#195214: .iso conflict, discussion of resolution
On Sat, Aug 30, 2003 at 02:13:10PM +0200, Stephan Kulow <[EMAIL PROTECTED]> wrote: > Am Saturday 30 August 2003 08:06 schrieb Chris Cheney: > > Would it be possible to get the two desktop filesi mentioned below merged > > into kdelibs so that arson and k3b are easily installable at the same time? > > I can do the commit myself if you approve. > > > Approved. > > Greetings, Stephan Thank you, guys. I will remove the files from arson. I'm glad we were able to get a resolution here. :) -- Mike Markley <[EMAIL PROTECTED]> GPG: 0x3B047084 7FC7 0DC0 EF31 DF83 7313 FE2B 77A8 F36A 3B04 7084
Re: Bug#195214: .iso conflict, discussion of resolution
On Sat, Aug 30, 2003 at 08:17:05PM +0200, Simon Richter <[EMAIL PROTECTED]> wrote: > This sounds like you may want to use an alternative here, so that the > sysadmin can choose which program to associate .iso files with by > default. Of course, users must be able to override this, but I think > that is given (is it?). > > Alternatives will have to be supported by any package that brings such a > file, but need no support from unrelated packages. Putting the file in > question into a base package is bad because it may associate the file > with a program that is not installed. I misspoke about the purpose; these files don't actually associate file types, just describe them. The only reasona arson and k3b both provide them is that nothing else currently does. -- Mike Markley <[EMAIL PROTECTED]> GPG: 0x3B047084 7FC7 0DC0 EF31 DF83 7313 FE2B 77A8 F36A 3B04 7084
