From: Michael Orlitzky <mjo@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: acct-group packages ??
Date: Mon, 5 Aug 2019 09:17:17 -0400 [thread overview]
Message-ID: <4cfff72b-8b62-f3e3-1414-def00f873d28@gentoo.org> (raw)
In-Reply-To: <20190805082110.5769e1ac@digimed.co.uk>
On 8/5/19 3:21 AM, Neil Bothwick wrote:
> On Sun, 4 Aug 2019 09:59:06 -0700, Ian Zimmerman wrote:
>
>> I see, I got caught (again) by the favorite gentoo sleight of hand of
>> updating a package and not bumping its version. In my case, eudev.
>
> 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.
next prev parent reply other threads:[~2019-08-05 13: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 [this message]
2019-08-06 8:17 ` Neil Bothwick
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=4cfff72b-8b62-f3e3-1414-def00f873d28@gentoo.org \
--to=mjo@gentoo.org \
--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