Though I don't have much bg on this issue, Package-groups is a way to determine which pkgs get pulled down and installed on a certain image.
Why would this not work in this case? rs On 7/15/11 8:41 AM, "Clark, Joel" <[email protected]> wrote: >See bug 20276. so tracker does not work right if GVolumeMonitor does not >work. GVolumeMonitor does not work if gvfs is not included in image >(it's not in IVI image). What's the right way in the build system to >tell the build tool it needs to put gvfs in every image that uses tracker? > >See Aleksander's note below as to why it's not a "depends" of the tracker >package. > >regards >Joel > > >-----Original Message----- >From: [email protected] [mailto:[email protected]] >Sent: Friday, July 15, 2011 6:33 AM >To: Clark, Joel >Subject: [Bug 20276] Tracker fail to find the media files from USB disk. > >https://bugs.meego.com/show_bug.cgi?id=20276 > >--- Comment #37 from aleksander <[email protected]> 2011-07-15 >13:33:10 UTC --- >(In reply to comment #36) >> Seems like a bug in the tracker packaging that it does not correctly >>specify >> it's dependencies. Fix this and the required dependencies will get >>added to the >> builds that are trying to use tracker > >Well, Tracker has never depended on gvfs directly, in any distribution I >know >of at least. Tracker usually depends just on GLib/GIO, but as gvfs is >optional, >glib packaging will also not depend on gvfs. Just happens that without the >gvfs-based backend in GLib, GVolumeMonitor cannot properly create volumes >from >mounts. Don't know. but it feels strange to require Tracker depend on >gvfs so >that the gvfs-based backend is used in GVolumeMonitor. Why not just >assume that >gvfs-based GIO is better, and directly add gvfs in the essentials >collection in >MeeGo? Or at least, make the packaging dependency in glib/gio itself? > >-------- >Product: OS Middleware >Component: Content framework (tracker) >MeeGo Release: 1.2.0 >Severity: normal >Priority: High >Keywords: >Status: NEW >Who: [email protected] >Assigned To: [email protected] >Target Build: --- >Flags: >Changed: >-------- > >https://bugs.meego.com/show_bug.cgi?id=20276 > > >-- >Configure bugmail: https://bugs.meego.com/userprefs.cgi?tab=email >------- You are receiving this mail because: ------- >You are on the CC list for the bug. >You reported the bug. >_______________________________________________ >MeeGo-packaging mailing list >[email protected] >http://lists.meego.com/listinfo/meego-packaging _______________________________________________ MeeGo-packaging mailing list [email protected] http://lists.meego.com/listinfo/meego-packaging
