On Wed, Jul 08, 2009 at 11:45:27AM -0700, Steve Langasek wrote: > On Wed, Jul 08, 2009 at 08:00:26PM +0200, Jan Hauke Rahm wrote: > > On Wed, Jul 08, 2009 at 07:55:59PM +0200, Jakub Wilk wrote: > > > * Jan Hauke Rahm <info@jhr-online.de>, 2009-07-08, 19:36: > > > >I'd like to have a new virtual package 'x-image-viewer'. All packages > > > >providing that virtual package should be able to view images in common > > > >formats (png, jpeg etc.). I'm thinking but that's pretty much all I can > > > >say... It's obvious that I would want all image viewers to provide that > > > >virtual package then. > > > And such a package is needed because...? > > > ...I'm working on a QA upload of xcftools which recommends basically all > > x-image-viewers. It contains a program that is a wrapper script that > > flattens an XCF image and displays it using an external PNG/PPM viewer. > > > I thought there might be more cases out there and thus started this > > thread. If you all scream no, I'm fine with that, too. Just tell me :-P > > How does xcftools actually invoke the external viewer? Does it have a long > list of commands to try? Basically egrep '^image/(png|x-portable-pixmap)\s*;\s*((\S*).*?)\s*($|;.*)' /etc/mailcap > A virtual package only makes sense if it will also provide a standard > interface that other packages will invoke. It doesn't have such, it just chooses one out the list provided by the command above (it's actually perl but anyways). Hauke
Attachment:
signature.asc
Description: Digital signature