On 01/20/2015 12:13 AM, Alexis Ballier wrote: > On Mon, 19 Jan 2015 20:31:45 +0100 > Michał Górny <[email protected]> wrote: >> 2. Subslots work correctly. Rebuilds are forced when the chosen >> library is upgraded. Moreover, USE flag change causes a rebuild when >> user decides to change the ffmpeg provider. > > > No offense, but this argument is complete crap. You should rather fix > portage bugs than propose to introduce tree-wide changes to hide them... > More precisely: || ( a:= b c:= d ) is perfectly defined (in the "what > it means" sense, not in PMS sense). When the package is built, if 'a' is > satisfied then a (and its subslot) is added to the subslot list of the > package; ditto for c. You end up with a list of subslot deps, that you > can store in vdb or whatever, and use that to decide when to rebuild > the package.
That's an interesting proposal, but I immediately find myself questioning how closely it models reality. For example, maybe the package links to both the a:= package and c:= package, or maybe just to one of them. Shouldn't our model match reality as closely as possible, as long as it's practical? -- Thanks, Zac
