public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Patrick Lauer <patrick@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Subslots: should they be bumped like SONAME or on any ABI changes?
Date: Sun, 15 Jun 2014 07:41:55 +0800	[thread overview]
Message-ID: <3245038.ZrpqGKPg2K@localhost> (raw)
In-Reply-To: <1402761029.16949.1.camel@rook>

On Saturday 14 June 2014 11:50:29 Alexandre Rostovtsev wrote:
> On Sat, 2014-06-14 at 16:13 +0100, Ciaran McCreesh wrote:
> > On Sat, 14 Jun 2014 16:41:51 +0200
> > 
> > Michał Górny <mgorny@gentoo.org> wrote:
> > > However, this means that we force much more rebuilds than necessary.
> > 
> > This shouldn't be considered to be a problem.
> 
> This would be suicide for Gentoo as a distro. Organizations that have a
> dedicated build server and a standardized /etc/portage config tree
> pushed to all user machines could rebuild half of @world once a week.
> Individual users running Gentoo on a single workstation or server can't
> and won't.

Well, you have to rebuild half of everything anyway. (And if you don't want to 
do that - update less often)

Last updates on my notebook had on average half a dozen packages needing to be 
rebuilt due to preserved-libs. 

How is that better than automated rebuilds that actually reduce the 
interaction I have with that machine?


I'd strongly prefer a coherent policy for this whole library versioning 
situation, maybe per-library (so instead of forcing everything to use subslots 
we say "all consumers of this lib have to, and ignore others for now)


  parent reply	other threads:[~2014-06-14 23:42 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-14 14:41 [gentoo-dev] Subslots: should they be bumped like SONAME or on any ABI changes? Michał Górny
2014-06-14 15:13 ` Ciaran McCreesh
2014-06-14 15:32   ` hasufell
2014-06-14 15:45     ` Ciaran McCreesh
2014-06-14 16:04       ` Georg Rudoy
2014-06-14 16:16       ` hasufell
2014-06-14 16:19         ` Ciaran McCreesh
2014-06-14 16:25           ` hasufell
2014-06-14 15:50   ` Alexandre Rostovtsev
2014-06-14 15:56     ` Ciaran McCreesh
2014-06-14 16:17       ` Alexandre Rostovtsev
2014-06-14 16:31         ` Ciaran McCreesh
2014-06-14 16:35           ` Alexandre Rostovtsev
2014-06-14 20:00           ` Rich Freeman
2014-06-14 23:41     ` Patrick Lauer [this message]
2014-06-14 16:05 ` Ian Stakenvicius
2014-06-14 16:10   ` [gentoo-dev] " Michael Palimaka
2014-06-14 16:23   ` [gentoo-dev] " hasufell
2014-06-14 16:50 ` Alexandre Rostovtsev
2014-06-14 16:57   ` Alexandre Rostovtsev
2014-06-14 17:13   ` [gentoo-dev] " Michael Palimaka
2014-06-16  9:47   ` [gentoo-dev] " Pacho Ramos
2014-06-16 10:54     ` Rich Freeman
2014-06-15 19:13 ` Matt Turner
2014-06-16  9:44 ` Pacho Ramos

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=3245038.ZrpqGKPg2K@localhost \
    --to=patrick@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