From: Kent Fredric <kentnl@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] News Item: Portage Dynamic Deps
Date: Wed, 24 Jan 2018 20:05:41 +1300 [thread overview]
Message-ID: <20180124200507.7bc87ba4@katipo2.lan> (raw)
In-Reply-To: <20180122164513.421c9390@snowtea>
[-- Attachment #1: Type: text/plain, Size: 661 bytes --]
On Mon, 22 Jan 2018 16:45:13 +0000
Ciaran McCreesh <ciaran.mccreesh@googlemail.com> wrote:
> perl-cleaner is rather strong evidence that the Perl situation needs a
> major change anyway...
perl-cleaner is now *mostly* redundant. Its only residual use is
catching circumstances where slot dependencies weren't adequately
provided early enough for them to work.( ~1% of cases )
dev-lang/perl also has additional papering over now that aims to
increase the number of situations where subgraphs of the dependency
graph that don't require C based extensions may continue to work while
portage is still "rebuild pending" on those parts of the graph.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-01-24 7:06 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-22 7:01 [gentoo-dev] News Item: Portage Dynamic Deps Zac Medico
2018-01-22 8:24 ` Alexis Ballier
2018-01-24 20:48 ` Zac Medico
2018-01-22 9:38 ` Dirkjan Ochtman
2018-01-24 20:53 ` Zac Medico
2018-01-22 10:28 ` Andreas K. Huettel
2018-01-22 10:53 ` James Le Cuirot
2018-01-22 16:43 ` Ian Stakenvicius
2018-01-22 16:45 ` Ciaran McCreesh
2018-01-24 7:05 ` Kent Fredric [this message]
2018-01-22 16:59 ` Michał Górny
2018-01-23 12:40 ` [gentoo-dev] " Michael Palimaka
2018-01-23 13:10 ` Rich Freeman
2018-01-23 13:15 ` Michael Orlitzky
2018-01-23 13:40 ` Michael Palimaka
2018-01-23 17:12 ` Rich Freeman
2018-01-24 10:31 ` Martin Vaeth
2018-01-24 11:16 ` Ulrich Mueller
2018-01-24 12:36 ` Martin Vaeth
2018-01-24 16:36 ` Ulrich Mueller
2018-01-24 20:58 ` [gentoo-dev] " Zac Medico
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=20180124200507.7bc87ba4@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