On 09/27/2012 01:30 PM, Ian Stakenvicius wrote: > On 27/09/12 04:13 PM, Zac Medico wrote: >> On 09/27/2012 12:53 PM, Brian Harring wrote: >>> Bullshit. This is optional in the sense of embrace/extend >>> 'optional'; if one PM takes up the new functionality, all have to >>> switch to writing unfinalized deps to the VDB, and all have to >>> switch to transfering that IUSE_RUNTIME crap to the VDB. > >> I think the proposal suddenly becomes a lot saner if it's done as >> an EAPI extension, the optional runtime deps and IUSE_RUNTIME >> conditionals are isolated in a new separate variable (perhaps >> SRDEPEND), and IUSE_RUNTIME is not allowed to intersect with IUSE. >> Using a separate SRDEPEND variable means that the package manager >> only has to preserve USE conditionals in the vdb for that one >> variable. > > > Saner, perhaps, but that would also mean the feature would be more or > less independent of the current USE handling within the PM.
Well, the package manager could still treat IUSE_RUNTIME flags as valid flags for things like USE deps in _other_ packages. So, they don't have to be entirely independent. The idea is just to limit the scope where those flags are allowed the package that declares the flags as runtime flags, so that those runtime flags are only allowed in SRDEPEND. > Mind you if it's easier to deal with in the PM then I guess > piggy-backing on the current USE implementation isn't an advantage. Part of my concern is not just the implementation details, but also being able to explain/document for communication purposes. If it's such a mess that it's difficult to communicate, then it sucks for everyone involved. -- Thanks, Zac
