public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: acct-group packages ??
Date: Tue, 6 Aug 2019 09:17:31 +0100	[thread overview]
Message-ID: <20190806091731.6998e0d1@phoucgh.digimed.co.uk> (raw)
In-Reply-To: <4cfff72b-8b62-f3e3-1414-def00f873d28@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1516 bytes --]

On Mon, 5 Aug 2019 09:17:17 -0400, Michael Orlitzky wrote:

> > I've not checked lately, but policy was that if an ebuild change did
> > not result in differences in the installed files, there was no need
> > for a version bump. This avoids needless recompiling of packages.
> >   
> 
> Realistically, almost all ebuild changes should incur a new revision. I
> would much rather recompile 100 packages *and have it work* than compile
> 10 packages and have it crash three times requiring manual intervention
> because the tree is so screwed up.
> 
> We have better guidelines these days:
> 
> https://devmanual.gentoo.org/general-concepts/ebuild-revisions
> 
> but they still give developers too much freedom to be lazy and commit
> important changes without a revision. The "straight to stable" advice
> contradicts our existing stabilization policy, and the USE flag advice
> says that you can rely on a non-default, portage-only feature to prevent
> breakage.

That's pretty much how I remember it. If the existing version crash, then
the binaries have changed so it should be bumped, but if a dev missed out
a new DEPEND for chromium of libreoffice that I happen to have already
installed, I don't want to have to waste hours of CPU time recompiling to
exactly the same end point.

The most important statement in the policy is also the hardest to enforce
"Developers are encouraged to use common sense" :-O


-- 
Neil Bothwick

What is a "free" gift ? Aren't all gifts free?

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2019-08-06  8:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-03 16:30 [gentoo-user] acct-group packages ?? Ian Zimmerman
2019-08-03 17:21 ` Neil Bothwick
2019-08-03 17:35   ` Mick
2019-08-04 16:59   ` [gentoo-user] " Ian Zimmerman
2019-08-05  7:21     ` Neil Bothwick
2019-08-05 13:17       ` Michael Orlitzky
2019-08-06  8:17         ` Neil Bothwick [this message]

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=20190806091731.6998e0d1@phoucgh.digimed.co.uk \
    --to=neil@digimed.co.uk \
    --cc=gentoo-user@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