On 2013-02-11, at 3:53 PM, James Cloos <[email protected]> wrote:
>>>>>> "AB" == Alexis Ballier <[email protected]> writes: > > AB> Well, if we have to advertise the usage of this option that basically > AB> disables subslot rebuilds, it only means we are doing something > AB> seriously wrong with subslots :=) > > So far, I've found the sub slots to be more of a pain in the ass than > helpful. > > They get in the way of things like automated 'emerge --sync;emerge -upvDN', > since portage craps out complaining about the subslots rather than showing > the list of what need to be built. > > Perhaps that is just an implementation detail to be worked out, but for now > they haven't done anything helpful here. this must be an implementation detail... the point of subslots and slot operators is to allow the revdep-rebuilds to be inlined so that low library updates don't break later application emerges during the -uDN ... the output should be the same as a "emerge -uDNpv world" plus a "revdep-rebuild -p" once everything is subslotted... it shouldn't affect your usual emerge process beyond that. is the conflict that emerge craps out on a subslot specific thing or is it a regular slot conflict made harder to read? > > -JimC > -- > James Cloos <[email protected]> OpenPGP: 1024D/ED7DAEA6 >
