version bump from 0.27.1_p20140713 to 0.27.1_p20140817 now includes a large number of new dependencies which are not tied to use flags. For example, mythplugins pulls in dependency on media-libs/libiec61883, even if media-tv/mythtv is built with USE="-ieee1394". Would having use flags in mythplugins (or polling enabled use flags from the mythtv build) be a better way to manage? I am not sure if there was some major change upstream which now requires these for mythplugins specifically (independent of mythtv use flags) but thought I would file the bug to clarify. Reproducible: Always Steps to Reproduce: 1. emerge =media-plugins/mythtv-0.27.1_p20140817 Actual Results: media-libs/libiec61883 is pulled in automatically due to ebuild dependencies Expected Results: have use flag for ieee1394 which then enables or disables dependency on media-libs/libiec61883
I discovered a number of missing dependencies - these have been missing for a while now so the only change in the ebuild is capturing them. Most seem to be "automagic" and I agree that they should be USE-based where possible. I need to take more time to go through the build system and enable this, so I'll leave this open to track. If you were using mythplugins without some of these deps without issue it will probably continue to work fine in the new version. However, if you do have some of these deps installed and they are upgraded, mythplugins could break due to linking errors. The new dependencies use slot operators so where the libraries declare subslots we should get automatic rebuilds.
*** Bug 520658 has been marked as a duplicate of this bug. ***
Ok, I see what is going on here. Mythplugins inherits configuration from mythtv, so if mythtv is built with ieee1394, then mythplugins will be as well, with no way to enabled/disable this (aside from patching). So, I think the cleanest option is to remove any deps inherited from mythtv which are optional. That means that things like firewire will be optional and triggered by the mythtv settings. On the other hand, if you upgrade firewire it will break linking on mythplugins and there won't be any automatic rebuilds, which was one of the goals of declaring the dependency.
I am not sure if any of the plugins actually need those dependencies but could you instead make mythplugins with USE flag ieee1394 that depends both on the actual libraries (which would trigger the automatic rebuild as needed) but also depend on mythtv with USE flag ieee1394 enabled? Same logic could be applied to other optional use flags with the mythtv package (theora, vorbis, fftw as other examples). The thought here is that I don't think we want myth and mythplugins built with different USE flags with common dependencies (can see issue where plugins are built with one but mythtv package is not) but need mythplugins to auto rebuild when the libraries are updated.
(In reply to Paul Sands from comment #4) > I am not sure if any of the plugins actually need those dependencies but > could you instead make mythplugins with USE flag ieee1394 that depends both > on the actual libraries (which would trigger the automatic rebuild as > needed) but also depend on mythtv with USE flag ieee1394 enabled? Same logic > could be applied to other optional use flags with the mythtv package > (theora, vorbis, fftw as other examples). > That's actually a great idea. Normally using USE flags ONLY to pull in deps is frowned upon. However, in this particular case it actually makes a lot of sense. While it is a bit indirect, the USE flag would be coupled to the on-disk image.
This has been fixed in the rich0 overlay. I'll leave this open until I push this into the tree in a few days, but feel free to test it in the meantime.
in portage now
