On 08/31/2012 01:46 PM, Ciaran McCreesh wrote: > On Fri, 31 Aug 2012 13:03:00 -0700 > What exactly would the rules be for handling a package that is in both > DEPEND and HDEPEND, when ROOT is in effect? Would the versions be > expected to match? What about use flags?
For the sake of simplicity, I would treat them as entirely independent. It should be easy enough for users to apply manual configuration adjustments in order to resolve any conflicts of this nature that may arise. If there turns out to be a strong demand for additional constraints, we can consider adding them in a future EAPI (possibly using a combined DEPENDENCIES variable). > Also, we're getting rather a lot of *DEPEND variables here... If we're > making people make major changes to their deps, which for HDEPEND we > definitely would be, Well, I not sure that "major changes" is a really good characterization. We're just talking about migrating a few things from DEPEND to HDEPEND, and it's not strictly required. The migration is only needed when fulfilling a request to support cross-compilation in a particular ebuild. > then the "it's expensive since people would have > to redo their deps" argument against a combined DEPENDENCIES variable > goes out of the window, so we should rethink that too. -- Thanks, Zac
