From: Rich Freeman <rich0@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] Subslots: should they be bumped like SONAME or on any ABI changes?
Date: Sat, 14 Jun 2014 16:00:15 -0400 [thread overview]
Message-ID: <CAGfcS_nhCe6xUBNnGgzdhjz8+uCfxoyvfYB4220T03Jta8V-eQ@mail.gmail.com> (raw)
In-Reply-To: <20140614173147.277d6974@googlemail.com>
On Sat, Jun 14, 2014 at 12:31 PM, Ciaran McCreesh
<ciaran.mccreesh@googlemail.com> wrote:
> On Sat, 14 Jun 2014 12:17:52 -0400
> Alexandre Rostovtsev <tetromino@gentoo.org> wrote:
>> On Sat, 2014-06-14 at 16:56 +0100, Ciaran McCreesh wrote:
>> > On Sat, 14 Jun 2014 11:50:29 -0400
>> > Alexandre Rostovtsev <tetromino@gentoo.org> 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.
>> >
>> > Then either Gentoo should ship binary packages, or the user should
>> > find another distribution.
>> >
>> > Gentoo *already* does a full rebuild for packages whose bumps or
>> > revbumps just result in one text file changing. So long as there
>> > isn't a mechanism and full ebuild support in place to prevent this,
>> > it's a silly argument.
>>
>> You don't see the difference between unnecessarily rebuilding one
>> package (because a text file changed) and unnecessarily rebuilding a
>> hundred packages (because libfoo added a new function)? Especially
>> since maintainers of packages with long compile times understandably
>> tend to be a bit conservative with their revision bumps, but have no
>> control over when their package's dependencies get subslotbumped.
>
> So why isn't there a call for a feature to make ebuilds not recompile
> the nine out of ten libraries and binaries that they provide that
> haven't changed on a bump?
This argument basically amounts to Portage isn't perfect, therefore we
shouldn't make it better.
The fact that some events cause unnecessary rebuilds doesn't mean that
we need to accept that other events cause unnecessary rebuilds.
Otherwise, who needs subslots at all - just make portage rebuild every
installed package on every install and we'll never be inconsistent.
:)
Rich
next prev parent reply other threads:[~2014-06-14 20:00 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 [this message]
2014-06-14 23:41 ` Patrick Lauer
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=CAGfcS_nhCe6xUBNnGgzdhjz8+uCfxoyvfYB4220T03Jta8V-eQ@mail.gmail.com \
--to=rich0@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