Picking random email...
02.10.14 22:48, Michał Górny написав(ла):
What is the status here?
signature.asc
Description: OpenPGP digital signature
On Sun, 09 Nov 2014 07:33:44 +0800
Patrick Lauer wrote:
> instead of trying to write a dependency resolution algorithm that
> assumes the Riemann Hypothesis is correct.
Thank you for your contribution to this thread. I just realised that if
we assume the Generalised Riemann Hypothesis, we can red
On Sat, 08 Nov 2014 22:52:24 +0100
Jauhien Piatlicki wrote:
> So the problem is only with intervals?
No. Intervals are one of many examples.
> I would really like to see a list of them all.
That could be rather tricky... I doubt anyone has a complete list,
particularly since most of the crazy d
On Sat, 8 Nov 2014 16:30:04 -0500
Rich Freeman wrote:
> if you have the second dep installed
Unfortunately the notion of "installed" is where most of the mess with
|| dependencies comes from...
What about "not installed yet, but will be installed during this
resolution"?
What about "an earlier
On Sat, 08 Nov 2014 20:01:54 +0100
Matthias Dahl wrote:
> Sorry to chime in like that but if you don't mind, I'd like to ask
> for a real-life example for badly declared dependencies with a few
> words why those are bad and how to make them actually better?
https://bugs.gentoo.org/show_bug.cgi?id
On 08/11/14 20:49, Thomas Kahle wrote:
> it seems to be a quasi-standard in the tree to use REQUIRED_USE
> if the tests of some package need USE flags. However, repoman
> complains:
>
> REQUIRED_USE.syntax 1
>media-libs/leptonica/leptonica-1.71-r1.ebuild: REQUIRED_USE: USE flag
>
TL;DR: perl-module.eclass gets a well-defined and documented API. You may see
some harmless "eqawarn" warnings from your ebuilds over the next time; either
fix them yourself according to the warning message or just wait until the
warnings are gone again. Overlay ebuilds will need to be fixed.
On 11/08/2014 10:53 PM, Andrew Savchenko wrote:
> On Sat, 08 Nov 2014 15:45:30 -0800 Zac Medico wrote:
>> On 11/08/2014 03:33 PM, Patrick Lauer wrote:
>>> We can choose for "code that works reasonably fast" - portage hasn't
>>> gotten any noticeable work on performance in a while, and people have
>
