Re: Bug#195214: .iso conflict, discussion of resolution
- To: Simon Richter <sjr@debian.org>, 195214@bugs.debian.org
- Cc: Christian Surchi <csurchi@debian.org>, Jean-Michel Kelbert <jean-michel@kelbert.com>, Chris Cheney <ccheney@cheney.cx>, debian-devel@lists.debian.org
- Subject: Re: Bug#195214: .iso conflict, discussion of resolution
- From: Mike Markley <mike@markley.org>
- Date: Sat, 30 Aug 2003 15:17:23 -0700
- Message-id: <[🔎] 20030830221723.GN1248@madhack.com>
- Mail-followup-to: Simon Richter <sjr@debian.org>, 195214@bugs.debian.org, Christian Surchi <csurchi@debian.org>, Jean-Michel Kelbert <jean-michel@kelbert.com>, Chris Cheney <ccheney@cheney.cx>, debian-devel@lists.debian.org
- In-reply-to: <[🔎] 20030830181705.GB802@phobos.fs.tum.de>
- References: <[🔎] 20030830053439.GJ1248@madhack.com> <[🔎] 20030830181705.GB802@phobos.fs.tum.de>
On Sat, Aug 30, 2003 at 08:17:05PM +0200, Simon Richter <sjr@debian.org> 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 <mike@markley.org>
GPG: 0x3B047084 7FC7 0DC0 EF31 DF83 7313 FE2B 77A8 F36A 3B04 7084
Reply to: