Re: .iso conflict, discussion of resolution
- To: Christian Surchi <csurchi@debian.org>, 195214@bugs.debian.org, Jean-Michel Kelbert <jean-michel@kelbert.com>, Chris Cheney <ccheney@cheney.cx>, debian-devel@lists.debian.org
- Subject: Re: .iso conflict, discussion of resolution
- From: Matt Zimmerman <mdz@debian.org>
- Date: Sat, 30 Aug 2003 18:08:17 -0400
- Message-id: <[🔎] 20030830220817.GW20504@alcor.net>
- Mail-followup-to: Christian Surchi <csurchi@debian.org>, 195214@bugs.debian.org, Jean-Michel Kelbert <jean-michel@kelbert.com>, Chris Cheney <ccheney@cheney.cx>, debian-devel@lists.debian.org
- In-reply-to: <[🔎] 20030830053439.GJ1248@madhack.com>
- References: <[🔎] 20030830053439.GJ1248@madhack.com>
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?
--
- mdz
Reply to: