upstream glibc has dropped support for older Linux kernels. your choices:
- upgrade your kernel
- switch to a different C library
- stick with glibc-2.19 for a while
be warned though there are no plans atm to backport things to glibc-2.19.
this includes security fixes, but more importantly a
On 03/08/14 16:16, Mike Frysinger wrote:
> upstream glibc has dropped support for older Linux kernels. your choices:
> - upgrade your kernel
> - switch to a different C library
> - stick with glibc-2.19 for a while
>
> be warned though there are no plans atm to backport things to glibc-2.19.
Steven J. Long wrote:
>
> collect your thoughts into a forum post
You are right: Not everybody on this list is interested in all
technical details, so it is perhaps better to shift this discussion
to the forums. I have opened the topic
https://forums.gentoo.org/viewtopic-p-7593700.html#7593700
Hello, everyone.
I would like to hear your opinion on what should be the meaning and use
of '|| ( A:= B:= )' dependencies.
By the PMS-y definition, any-of dependency can be satisfied by either
branch of it, and the provider can be safely switched at runtime. That
is:
|| ( A B )
means that ei
The attached list notes all of the packages that were added or removed
from the tree, for the week ending 2014-08-03 23h59 UTC.
Removals:
virtual/perl-Class-ISA 2014-08-02 19:56:52 dilfridge
virtual/perl-Filter 2014-08-02 19:58:55 dilfridge
Additions:
dev-util/objconv
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 03/08/14 06:44 PM, Michał Górny wrote:
> Hello, everyone.
>
> I would like to hear your opinion on what should be the meaning and
> use of '|| ( A:= B:= )' dependencies. [ Snip! ]
I mentioned this on irc on Friday; as I understand it the followi
> On Mon, 4 Aug 2014, Michał Górny wrote:
> In particular, I was thinking we could reuse this syntax:
> || ( A:= B:= )
> to express any-of dependencies that do not support runtime switching
> of providers -- since that is pretty much what := does to slots.
> This would save us from creating
