This does seem to break distcheck, however, because update-mime-database leaves a bunch of stuff in the _build directory. Perhaps we should add DISTCHECK_CONFIGURE_FLAGS = --disable-update-mimedb to Makefile.am? ----- Original Message ----- > From: "Christophe Fergeau" <cfergeau@xxxxxxxxxx> > To: "Marc-André Lureau" <mlureau@xxxxxxxxxx> > Cc: "virt" <virt-tools-list@xxxxxxxxxx> > Sent: Wednesday, December 18, 2013 9:09:35 AM > Subject: Re: [virt-viewer] Update shared mime database on install/uninstall > > On Wed, Dec 18, 2013 at 06:34:08AM -0500, Marc-André Lureau wrote: > > ----- Original Message ----- > > > I've tested that on a fresh f20 install, if I install virt-viewer, > > > gvfs-info does not return the right mime type for .vv files. > > > On my laptop, it's working, but I suspect I ran update-mime-database by > > > hand at some point for some reason I don't remember. > > > > I probably did the same, then, perhaps a yum does it automatically on > > update? > > Oh, what can have happened is that another package installation triggered the > update-mime-database call. I doubt yum would run it on its own on update, > but not on installation of packages. I've tested that things are not > working as expected on a fresh f20 install until you run > update-mime-database (ie same issue as in the bug report). > > Christophe > > _______________________________________________ > virt-tools-list mailing list > virt-tools-list@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/virt-tools-list _______________________________________________ virt-tools-list mailing list virt-tools-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/virt-tools-list
