-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 11/08/15 03:13 PM, Gregory Woodbury wrote:
Is a possible solution something like an eselect module to
indicate the preferred interface kit? It could default to any
package that is available with a sequential set of preferred
order. Then
I've cherry-picked the recent repoman changes for the new git tree onto
a new branch starting at the 2.2.20 release. This should take care of
all the recent flood of emails about the new workflow. I also included
a few man page corrections and improvements.
Future:
I hope to get the repoman
On Tue, 11 Aug 2015 23:30:31 +1000
Michael Palimaka kensing...@gentoo.org wrote:
I invite you to reproduce the problem yourself then make the
judgement. Using REQUIRED_USE like this makes the affected packages
unusable.
Can't we all (except for the usual suspect) just agree that REQUIRED_USE
On 11 Aug 2015 10:45, Anthony G. Basile wrote:
On 8/11/15 10:33 AM, Ian Stakenvicius wrote:
On 11/08/15 06:11 AM, Leno Hou wrote:
I think ppc64le would become popular,
https://en.wikipedia.org/wiki/Ppc64.
1. enable porting x86 Linux based application with minimal effort.
2. Some
On 11 Aug 2015 10:49, James Le Cuirot wrote:
If ppc64le does become popular then I would suggest that we drop 32-bit
ppc first. Others may disagree though. :)
ppc isn't being dropped, and ppc64le is entirely orthogonal to support for it
-mike
signature.asc
Description: Digital signature
101 - 105 of 105 matches
Mail list logo
