public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Kent Fredric <kentnl@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: pkg_rm_pretend?
Date: Sun, 15 Oct 2017 17:31:24 +1300	[thread overview]
Message-ID: <20171015173124.113b7eb5@katipo2.lan> (raw)
In-Reply-To: <pan$465a2$3285dd26$150a2d5c$cc63b8d2@cox.net>

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

On Sun, 15 Oct 2017 04:17:49 +0000 (UTC)
Duncan <1i5t5.duncan@cox.net> wrote:

> I can also imagine doing something drastic like hourly depcleans, if 
> that's what it too, too, after dealing with a 1900-pkg-depclean!  Yikes!

It does sound like a lot, but when you have minimal chroots with only 9
entries in world, something like say, khtml gets bumped, and I test it
because this line brings it to my attention: 

https://gitweb.gentoo.org/repo/gentoo.git/tree/kde-frameworks/khtml/khtml-5.39.0.ebuild#n56

That's easily 300 odd new deps.

Only to be cleaned maybe hours later so I can ensure my tests don't
fail due to missing deps.

Admittedly, half this stuff I probably don't *need* to test, I
sometimes re-test things just because somebody keyworded/stabilized a
package ... but my "Has changed" and "is perl" =-> "something broken?
Test me maybe?!" tools are pretty senseless in this regard.

Besides, a broad brush is better anyway.

And as long as I don't slack off for too many days, that backlog is
pretty manageable.

Not even doing reverse-dep testing, that's ... uh. Yeah, I'll let
toralf handle that, I'll just make sure the latest perl versions aren't
breaking things for now.

Sometime soon I'm hoping to move on to testing against development
releases of Perl again.

But eh, mountain.shovel while true;

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

      reply	other threads:[~2017-10-15  4:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-11 16:20 [gentoo-dev] pkg_rm_pretend? Kent Fredric
2017-10-11 16:44 ` Michael Orlitzky
2017-10-12  7:50 ` [gentoo-dev] pkg_rm_pretend? Duncan
2017-10-14 17:36   ` Kent Fredric
2017-10-15  4:17     ` Duncan
2017-10-15  4:31       ` Kent Fredric [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=20171015173124.113b7eb5@katipo2.lan \
    --to=kentnl@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