public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ian Stakenvicius <axs@gentoo.org>
To: "gentoo-dev@lists.gentoo.org" <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] On the good usage of subslots
Date: Mon, 11 Feb 2013 16:13:52 -0500	[thread overview]
Message-ID: <0E58786E-C742-4035-91C2-AF115F7FCB37@gentoo.org> (raw)
In-Reply-To: <m3a9rabmh7.fsf@carbon.jhcloos.org>



On 2013-02-11, at 3:53 PM, James Cloos <cloos@jhcloos.com> wrote:

>>>>>> "AB" == Alexis Ballier <aballier@gentoo.org> 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 <cloos@jhcloos.com>         OpenPGP: 1024D/ED7DAEA6
> 


  reply	other threads:[~2013-02-11 21:15 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-09 12:15 [gentoo-dev] On the good usage of subslots Alexis Ballier
2013-02-09 12:38 ` [gentoo-dev] " Michael Palimaka
2013-02-09 12:46   ` Alexis Ballier
2013-02-09 12:52   ` Alexis Ballier
2013-02-09 14:09     ` Michael Palimaka
2013-02-11  0:45       ` Alexis Ballier
2013-02-11 15:40     ` Ian Stakenvicius
2013-02-09 13:47 ` [gentoo-dev] " Samuli Suominen
2013-02-09 14:05   ` [gentoo-dev] " Michael Palimaka
2013-02-09 16:06     ` Zac Medico
2013-02-09 16:36       ` Michael Palimaka
2013-02-09 16:39         ` Samuli Suominen
2013-02-09 16:53           ` Pacho Ramos
2013-02-09 19:21 ` [gentoo-dev] " Michał Górny
2013-02-11  0:44   ` Alexis Ballier
2013-02-11 20:53     ` James Cloos
2013-02-11 21:13       ` Ian Stakenvicius [this message]
2013-02-11 21:21       ` Zac Medico

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0E58786E-C742-4035-91C2-AF115F7FCB37@gentoo.org \
    --to=axs@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox