From: Rich Freeman <rich0@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] EAPI 6 portage is out!
Date: Sat, 21 Nov 2015 16:00:44 -0500 [thread overview]
Message-ID: <CAGfcS_nTduMLdhL4gxAri5MBUTAPjTKm8m6KgLJHsJF0efzzEA@mail.gmail.com> (raw)
In-Reply-To: <20151121215121.b2e4a29f30ca2baa71d493ef@gentoo.org>
On Sat, Nov 21, 2015 at 1:51 PM, Andrew Savchenko <bircoph@gentoo.org> wrote:
>
> On Wed, 18 Nov 2015 07:01:21 -0500 Rich Freeman wrote:
>> On Wed, Nov 18, 2015 at 6:12 AM, Alexander Berntsen <bernalex@gentoo.org> wrote:
>> > When I do QA in projects I'm involved with (at least outside of
>> > Gentoo), we don't do it live on end-user systems. I'll leave the
>> > details as an exercise for the Gentoo developer.
>> >
>>
>> People who run ~arch are not really end-users - they're contributors
>> who have volunteered to test packages.
>
> I strongly disagree with you. We do not use stable even at
> enterprise grade production systems and HPC setups. Stable is just
> too freaking old in order to be usable for our purposes, not to
> mention that it lacks many packages at all. We tried stable
> several times, it just freaks out admins (including myself) too
> badly or results in horrible mess of stable and unstable which is
> less stable that unstable setups. I do not use stable at
> workstations and personal setups as well.
Interesting. I've had the opposite experience, and don't run ~arch
except for testing purposes. I don't hesitate to keyword packages
when necessary, and file bugs for their stabilization if appropriate.
Also, if you're doing something like HPC then you're probably focused
on a specific application, with your own QA system, so Gentoo's QA
doesn't really impact you much anyway as your own regression test is
going to catch issues. I'm not nearly that formal but I've
containerized almost all my services because I don't like relying on
Gentoo's QA. If I update my mariadb container I just make sure that
mariadb is working, and revert it if not. If it happens to contain a
broken ssh client it doesn't concern me at all, since I don't use that
container for ssh. Of course, the downside of this is that I end up
updating a lot of hosts, all for personal use.
> Of course I understand that there are people
> using it and I try to support stable packages as well, but these
> versions are mostly a burden and I can't really understand stable
> users.
Well, to be fair it seems like most Gentoo developers consider half
the tree a burden (that would be the "other" half). We all have our
itches that we're trying to scratch. As long as everybody follows the
policies the results end up working out reasonably well for everybody.
Some of us barely test ~arch at all, and others barely test stable at
all, and it seems that for the most part things work out.
In any case, the purpose of ~arch is testing, and is not intended to
be a stable experience, even if it often ends up being that way (which
is certainly nothing to complain about). If we added another layer of
testing above ~arch, all we'd see happen is that everybody who runs
~arch today would just switch to that, since it would essentially be
the same thing, and ~arch wouldn't really serve any purpose at all.
If the purpose of ~arch isn't testing, then why have it at all?
But, like I said, if somebody wants to volunteer to do a barrage of QA
tests on portage, by all means do so. It will only make life better
for everybody. I just don't see any reason to bar the portage authors
from introducing a version if they consider it suitable for testing.
--
Rich
next prev parent reply other threads:[~2015-11-21 21:00 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-17 22:09 [gentoo-dev] EAPI 6 portage is out! Michał Górny
2015-11-17 22:45 ` Michael Orlitzky
2015-11-17 23:35 ` Mike Gilbert
2015-11-18 1:04 ` Ian Stakenvicius
2015-11-18 2:22 ` Michael Orlitzky
2015-11-18 7:25 ` Ulrich Mueller
2015-11-18 9:25 ` Alexander Berntsen
2015-11-18 9:54 ` Raymond Jennings
2015-11-19 8:13 ` Daniel Campbell
2015-11-18 11:05 ` Ulrich Mueller
2015-11-18 11:12 ` Alexander Berntsen
2015-11-18 11:23 ` Ulrich Mueller
2015-11-18 11:26 ` Alexander Berntsen
2015-11-18 12:01 ` Rich Freeman
2015-11-18 12:06 ` Alexander Berntsen
2015-11-18 12:48 ` Rich Freeman
2015-11-21 4:35 ` Daniel Campbell
2015-11-20 9:39 ` Patrick Lauer
2015-11-20 12:34 ` Rich Freeman
2015-11-21 18:51 ` Andrew Savchenko
2015-11-21 21:00 ` Rich Freeman [this message]
2015-11-22 15:54 ` [gentoo-dev] " Michael Palimaka
2015-11-22 16:29 ` Dirkjan Ochtman
2015-11-22 16:41 ` Andreas K. Huettel
2015-11-23 7:26 ` Duncan
2015-11-18 15:09 ` [gentoo-dev] " Andreas K. Huettel
2015-11-18 11:59 ` Rich Freeman
2015-11-18 12:00 ` Alexander Berntsen
2015-11-18 15:10 ` Brian Dolbec
2015-11-18 16:47 ` Rich Freeman
2015-11-20 9:27 ` Ian Delaney
2015-11-18 16:47 ` [gentoo-dev] " »Q«
2015-11-18 17:06 ` Ulrich Mueller
2015-11-18 17:56 ` »Q«
2015-11-18 14:57 ` [gentoo-dev] " Andreas K. Huettel
2015-11-18 18:50 ` Ian Stakenvicius
2015-11-18 19:17 ` Andreas K. Huettel
2015-11-18 1:54 ` [gentoo-dev] " Duncan
2015-11-18 3:15 ` Rich Freeman
2015-11-18 1:20 ` [gentoo-dev] " NP-Hardass
2015-11-18 5:10 ` Michał Górny
2015-11-22 8:19 ` [gentoo-dev] " Martin Vaeth
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_nTduMLdhL4gxAri5MBUTAPjTKm8m6KgLJHsJF0efzzEA@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