Re: [gentoo-dev] [PATCH 1/1] kernel-2.eclass: Point user to additional kernel removal, instructions. See bug #581522.

2016-12-27 Thread Daniel Campbell
On 12/27/2016 04:52 PM, Mike Pagano wrote: > This addresses concerns that users might not realize that after an > unmerge of kernel sources some files will need to be removed manually. > The particular concern was specific to the files in /lib/modules/. I > liked this solution, since it does not

Re: [gentoo-dev] [PATCH 1/1] kernel-2.eclass: Point user to additional kernel removal, instructions. See bug #581522.

2016-12-27 Thread Alice Ferrazzi
looks like nice information to give :) ok, for me. On Wed, Dec 28, 2016 at 9:52 AM, Mike Pagano wrote: > This addresses concerns that users might not realize that after an > unmerge of kernel sources some files will need to be removed manually. > The particular concern was

[gentoo-dev] [PATCH 1/1] kernel-2.eclass: Point user to additional kernel removal, instructions. See bug #581522.

2016-12-27 Thread Mike Pagano
This addresses concerns that users might not realize that after an unmerge of kernel sources some files will need to be removed manually. The particular concern was specific to the files in /lib/modules/. I liked this solution, since it does not require a wordy explanation to be written in the

Re: [gentoo-portage-dev] [PATCH] binarytree._read_metadata: return empty strings for undefine values (bug 603826)

2016-12-27 Thread Zac Medico
On 12/27/2016 03:39 PM, Brian Dolbec wrote: > On Tue, 27 Dec 2016 13:33:55 -0800 > Zac Medico wrote: > >> Fix the binarytree._read_metadata method to return empty strings for >> undefined metadata values, in order to fulfill a contract with the >> _pkg_str class. This

Re: [gentoo-portage-dev] [PATCH] binarytree._read_metadata: return empty strings for undefine values (bug 603826)

2016-12-27 Thread Brian Dolbec
On Tue, 27 Dec 2016 13:33:55 -0800 Zac Medico wrote: > Fix the binarytree._read_metadata method to return empty strings for > undefined metadata values, in order to fulfill a contract with the > _pkg_str class. This prevents an AttributeError triggered by old > binary

Re: [gentoo-dev] [PATCH] toolchain.eclass: set CHOST for gcc-config calls

2016-12-27 Thread James Le Cuirot
On Tue, 27 Dec 2016 12:04:04 -0500 Mike Gilbert wrote: > For a typical cross-compiler build, CHOST is unchanged from the value > typically in make.conf, but CTARGET gets set to the "cross" arch. Yep. > In the case where we are cross-compiling a native compiler, CHOST >

Re: [gentoo-dev] [PATCH] toolchain.eclass: set CHOST for gcc-config calls

2016-12-27 Thread A. Wilcox
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 27/12/16 11:04, Mike Gilbert wrote: > What I'm very unsure of is cross-compiling a cross-compiler CBUILD > != CHOST != CTARGET. That requires a bit of thought. I'm not sure > we even really support that in toolchain.eclass though. > Having

Re: [gentoo-portage-dev] [PATCH] LinkageMapELF: compute mulilib category for preserved libs (bug 598080)

2016-12-27 Thread Zac Medico
On 12/27/2016 01:23 PM, Brian Dolbec wrote: > On Mon, 26 Dec 2016 20:37:39 -0800 > Zac Medico wrote: > >> When support for parsing ELF headers in order to compute multilib >> category was added in commit f1c1b8a77eebf7713b32e5f9945690f60f4f46de, >> the LinkageMapELF class was

[gentoo-portage-dev] [PATCH] binarytree._read_metadata: return empty strings for undefine values (bug 603826)

2016-12-27 Thread Zac Medico
Fix the binarytree._read_metadata method to return empty strings for undefined metadata values, in order to fulfill a contract with the _pkg_str class. This prevents an AttributeError triggered by old binary packages which have undefined repository metadata, as reported in bug 603826.

Re: [gentoo-portage-dev] [PATCH] LinkageMapELF: compute mulilib category for preserved libs (bug 598080)

2016-12-27 Thread Brian Dolbec
On Mon, 26 Dec 2016 20:37:39 -0800 Zac Medico wrote: > When support for parsing ELF headers in order to compute multilib > category was added in commit f1c1b8a77eebf7713b32e5f9945690f60f4f46de, > the LinkageMapELF class was not updated to do the same for preserved >

Re: [gentoo-dev] [PATCH] toolchain.eclass: set CHOST for gcc-config calls

2016-12-27 Thread Mike Gilbert
On Tue, Dec 27, 2016 at 6:10 AM, Joakim Tjernlund wrote: > On Tue, 2016-12-27 at 00:22 -0800, Daniel Campbell wrote: >> On 12/26/2016 12:22 PM, Mike Gilbert wrote: >> > Bug: https://bugs.gentoo.org/603776 >> > --- >> > eclass/toolchain.eclass | 8 >> > 1

Re: [gentoo-dev] [PATCH] toolchain.eclass: set CHOST for gcc-config calls

2016-12-27 Thread Mike Gilbert
On Tue, Dec 27, 2016 at 3:22 AM, Daniel Campbell wrote: > On 12/26/2016 12:22 PM, Mike Gilbert wrote: >> Bug: https://bugs.gentoo.org/603776 >> --- >> eclass/toolchain.eclass | 8 >> 1 file changed, 4 insertions(+), 4 deletions(-) >> >> diff --git

Re: [gentoo-dev] The changes about the stabilization process

2016-12-27 Thread Kent Fredric
On Sun, 25 Dec 2016 23:32:56 +0900 Aaron Bauman wrote: > It is not necessary to use a file now. Just put the list in the "Atoms to > stabilize" as described. Well, to an extent it was more a problem I feel the *need* to use this feature already ;) Because I have some stuff

Re: [gentoo-dev] [PATCH] toolchain.eclass: set CHOST for gcc-config calls

2016-12-27 Thread Joakim Tjernlund
On Tue, 2016-12-27 at 00:22 -0800, Daniel Campbell wrote: > On 12/26/2016 12:22 PM, Mike Gilbert wrote: > > Bug: https://bugs.gentoo.org/603776 > > --- > >  eclass/toolchain.eclass | 8 > >  1 file changed, 4 insertions(+), 4 deletions(-) > > > > diff --git a/eclass/toolchain.eclass

Re: [gentoo-dev] [PATCH] toolchain.eclass: set CHOST for gcc-config calls

2016-12-27 Thread Daniel Campbell
On 12/26/2016 12:22 PM, Mike Gilbert wrote: > Bug: https://bugs.gentoo.org/603776 > --- > eclass/toolchain.eclass | 8 > 1 file changed, 4 insertions(+), 4 deletions(-) > > diff --git a/eclass/toolchain.eclass b/eclass/toolchain.eclass > index 55249b00249b..97511ee12440 100644 > ---