Re: [gentoo-dev] Re: [gentoo-dev-announce] EAPI 6 draft for review

2015-10-20 Thread Daniel Campbell
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 10/17/2015 05:52 AM, Ulrich Mueller wrote: >> On Sat, 17 Oct 2015, hasufell wrote: > >>> 2. eapply_user really belongs in the PM, especially if it's run >>> by default. And it needs patch applying function. And if we >>> have to implement pa

Re: [gentoo-dev] Re: [gentoo-dev-announce] EAPI 6 draft for review

2015-10-20 Thread Alexis Ballier
On Mon, 19 Oct 2015 15:49:06 -0400 Rich Freeman wrote: > On Mon, Oct 19, 2015 at 2:28 PM, Alexis Ballier > wrote: > > > > However, as you say, putting it in cmake-utils needs to be properly > > thought so that it doesn't conflict with other eclasses: Hence the > > need to properly define what ec

Re: [gentoo-dev] Re: [gentoo-dev-announce] EAPI 6 draft for review

2015-10-20 Thread Alexis Ballier
On Tue, 20 Oct 2015 00:47:49 -0700 Daniel Campbell wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On 10/17/2015 05:52 AM, Ulrich Mueller wrote: > >> On Sat, 17 Oct 2015, hasufell wrote: > > > >>> 2. eapply_user really belongs in the PM, especially if it's run > >>> by d

Re: [gentoo-dev] News Item: Future Support of hardened-sources Kernel

2015-10-20 Thread Daniel Campbell
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 10/18/2015 06:36 PM, Anthony G. Basile wrote: > Hi everyone, for your consideration: > > Title: Future Support of hardened-sources Kernel Content-Type: > text/plain Posted: 2015-10-21 Revision: 1 News-Item-Format: 1.0 > Display-If-Installed: sys

Re: [gentoo-dev] News Item: Future Support of hardened-sources Kernel

2015-10-20 Thread Rich Freeman
On Tue, Oct 20, 2015 at 4:23 AM, Daniel Campbell wrote: > However, does this mean the hardened kernel package must stay in ~arch > since it's technically the testing version? Or would we keyword it > based on our own findings of stability? I'd recommend that the team does whatever adds the most v

Re: [gentoo-dev] Re: [gentoo-dev-announce] EAPI 6 draft for review

2015-10-20 Thread Rich Freeman
On Tue, Oct 20, 2015 at 3:51 AM, Alexis Ballier wrote: > On Mon, 19 Oct 2015 15:49:06 -0400 > Rich Freeman wrote: > > It's not about correctness vs convenience: eapply_user idempotent > doesn't prevent from doing it correctly. It makes it possible to do it > incorrectly though, just like any turi

Re: [gentoo-dev] News Item: Future Support of hardened-sources Kernel

2015-10-20 Thread Anthony G. Basile
On 10/20/15 4:23 AM, Daniel Campbell wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 10/18/2015 06:36 PM, Anthony G. Basile wrote: Hi everyone, for your consideration: Title: Future Support of hardened-sources Kernel Content-Type: text/plain Posted: 2015-10-21 Revision: 1 News-Item-F

Re: [gentoo-dev] Re: [gentoo-dev-announce] EAPI 6 draft for review

2015-10-20 Thread Alexis Ballier
On Tue, 20 Oct 2015 04:57:07 -0400 Rich Freeman wrote: > On Tue, Oct 20, 2015 at 3:51 AM, Alexis Ballier > wrote: > > On Mon, 19 Oct 2015 15:49:06 -0400 > > Rich Freeman wrote: > > > > It's not about correctness vs convenience: eapply_user idempotent > > doesn't prevent from doing it correctly.

Re: [gentoo-dev] News Item: Future Support of hardened-sources Kernel

2015-10-20 Thread Anthony G. Basile
On 10/20/15 4:45 AM, Rich Freeman wrote: On Tue, Oct 20, 2015 at 4:23 AM, Daniel Campbell wrote: However, does this mean the hardened kernel package must stay in ~arch since it's technically the testing version? Or would we keyword it based on our own findings of stability? I'd recommend that

Re: [gentoo-dev] Re: [gentoo-dev-announce] EAPI 6 draft for review

2015-10-20 Thread Rich Freeman
On Tue, Oct 20, 2015 at 5:22 AM, Alexis Ballier wrote: > > Ok, that's what I'd call "forced correctness" :) > But again, theory tells you that if you want algorithmically checkable > correctness then you have to seriously limit your possibilities, which > is why I usually don't even consider this

Re: [gentoo-dev] Re: [gentoo-dev-announce] EAPI 6 draft for review

2015-10-20 Thread Alexis Ballier
On Tue, 20 Oct 2015 06:00:15 -0400 Rich Freeman wrote: [...] > > > > First, eclasses shouldn't apply patches on their own but take what > > the ebuild tells it to apply: With multiple eclasses applying random > > patches on their own, you're already asking for trouble. > > Then, ebuild can just se

[gentoo-dev] new entry to metadata.dtd tag

2015-10-20 Thread Ian Delaney
A user wishes to set the remote-id type to gitlab where a package is located that he maintains. gitlab is both a software and a code hosting site. See https://bugs.gentoo.org/show_bug.cgi?id=563578 -- kind regards Ian Delaney

Re: [gentoo-dev] gcc-5 news item wrt C++ ABI

2015-10-20 Thread Mike Frysinger
On 03 Oct 2015 19:53, Anthony G. Basile wrote: > On 10/3/15 7:16 PM, hasufell wrote: > > On 10/03/2015 04:13 AM, Mike Frysinger wrote: > >> Title: GCC 5 Defaults to the New C++11 ABI > >> Author: Mike Frysinger > >> Content-Type: text/plain > >> Posted: 2015-10-02 > >> Revision: 1 > >> News-Item-F

[gentoo-dev] utilizing BASH_COMPAT to smooth upgrades

2015-10-20 Thread Mike Frysinger
On 16 Oct 2015 20:42, Ulrich Mueller wrote: > EAPI 6: Bash version is 4.2. do we want to mandate the BASH_COMPAT aspect in PMS ? or at least make into a recommendation ? https://bugs.gentoo.org/431340#c20 local maj=4 min=2 if ([[ ${BASH_VERSINFO[0]} -lt ${maj} ]] || [[ ${BASH_VERSINFO

[gentoo-dev] [warning] the bug queue has 86 bugs

2015-10-20 Thread Alex Alexander
Our bug queue has 86 bugs! If you have some spare time, please help assign/sort a few bugs. To view the bug queue, click here: http://bit.ly/m8PQS5 Thanks!

[gentoo-dev] Re: News Item: Future Support of hardened-sources Kernel

2015-10-20 Thread Duncan
Anthony G. Basile posted on Tue, 20 Oct 2015 05:34:33 -0400 as excerpted: > On 10/20/15 4:45 AM, Rich Freeman wrote: >> On Tue, Oct 20, 2015 at 4:23 AM, Daniel Campbell >> wrote: >>> However, does this mean the hardened kernel package must stay in ~arch >>> since it's technically the testing vers

Re: [gentoo-dev] utilizing BASH_COMPAT to smooth upgrades

2015-10-20 Thread Ulrich Mueller
> On Tue, 20 Oct 2015, Mike Frysinger wrote: >> EAPI 6: Bash version is 4.2. > do we want to mandate the BASH_COMPAT aspect in PMS ? > or at least make into a recommendation ? If I understand [1] correctly, coverage of BASH_COMPAT is incomplete: It only changes incompatible behaviour back to

[gentoo-dev] Re: stabilization commits and atomicity

2015-10-20 Thread Duncan
Rich Freeman posted on Mon, 19 Oct 2015 13:52:58 -0400 as excerpted: > On Mon, Oct 19, 2015 at 1:40 PM, hasufell wrote: >> On 10/19/2015 07:37 PM, Rich Freeman wrote: >>> >>> However, stabilizing a single package really is an impactful change. >>> The fact that you're doing 100 of them at one tim

Re: [gentoo-dev] utilizing BASH_COMPAT to smooth upgrades

2015-10-20 Thread Mike Frysinger
On 21 Oct 2015 00:03, Ulrich Mueller wrote: > > On Tue, 20 Oct 2015, Mike Frysinger wrote: > > >> EAPI 6: Bash version is 4.2. > > > do we want to mandate the BASH_COMPAT aspect in PMS ? > > or at least make into a recommendation ? > > If I understand [1] correctly, coverage of BASH_COMPAT i

[gentoo-dev] Re: stabilization commits and atomicity

2015-10-20 Thread Duncan
hasufell posted on Mon, 19 Oct 2015 19:13:50 +0200 as excerpted: > On 10/19/2015 07:08 PM, Rich Freeman wrote: >> On Mon, Oct 19, 2015 at 11:27 AM, Ian Stakenvicius >> wrote: >>> >>> Ahh, so what you're referring to here is stabilization of multiple >>> unrelated packages in a single commit.. ok

[gentoo-dev] Re: [gentoo-commits] repo/gentoo:master commit in: dev-python/intelhex/

2015-10-20 Thread hasufell
On 10/20/2015 04:02 PM, Mike Frysinger wrote: > commit: a68f2479fba9422913cb760166316bf489d72ca8 > Author: Vincent Palatin chromium org> > AuthorDate: Tue Oct 20 14:01:34 2015 + > Commit: Mike Frysinger gentoo org> > CommitDate: Tue Oct 20 14:01:50 2015 + > URL:https

[gentoo-dev] Re: [gentoo-dev-announce] EAPI 6 draft for review

2015-10-20 Thread Duncan
Alexis Ballier posted on Tue, 20 Oct 2015 12:25:07 +0200 as excerpted: > On Tue, 20 Oct 2015 06:00:15 -0400 Rich Freeman > wrote: > >> So, perhaps it is a fair question to ask what is the specific harm from >> allowing it to be a no-op on subsequent calls, other than encouraging a >> coding prac