On 23 November 2016 at 14:03, Chris Murphy <lists@xxxxxxxxxxxxxxxxx> wrote: > On Wed, Nov 23, 2016 at 10:36 AM, Adam Williamson > <adamwill@xxxxxxxxxxxxxxxxx> wrote: >> On Wed, 2016-11-23 at 10:33 -0800, Andrew Lutomirski wrote: >>> On Nov 23, 2016 10:12 AM, "Michael Catanzaro" <mcatanzaro@xxxxxxxxx> wrote: >>> > >>> > On Wed, 2016-11-23 at 16:36 +0100, Hans de Goede wrote: >>> > > I don't think that is entirely true. I've recently been trying >>> > > to get gnome3 to run on under-powered machines like cheap ARM >>> > > tablets, and I can do "dnf remove tracker" more or less just >>> > > fine, I loose totem due to some weird dependency chain, and I >>> > > think also gnome-documents which I guess is an issue for some >>> > > use-cases, but most of gnome will stay and work just fine. >>> > >>> > Besides those, also gnome-photos and gnome-music (which aren't >>> > installed by default currently, but will eventually be). And indexed >>> > search is really very important for nautilus. >>> >>> That's indexed search by *name*, right? I can't imagine *any* reason that >>> running a codec in the indexer is needed for nautilus. >> >> "I want to find all the files I have that are songs by Justin Bieber, >> so I can shoot them into outer space". > > Pretty sure such metadata is a function of the container format, e.g. > mp4, m4a, rather than the codec used for encoding the music or video > itself. It might be but because most people tie those two things together when they are writing code.. they get bundled together. This is why codecs have been such a rich target in Windows (and in some ways Mac) malware over the years. You get two channels to build an exploit for free :). > -- > Chris Murphy > _______________________________________________ > devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx -- Stephen J Smoogen. _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
