[EPEL-devel] Re: Adding the devtoolset repo for EPEL builds

2016-08-31 Thread Dominik 'Rathann' Mierzejewski
On Wednesday, 31 August 2016 at 10:58, dani wrote: [...] > As far as i could tell, the main argument against my scheme was usage of > /opt, yet it is approved for scl, despite scl's limitations. SCL was never approved for Fedora. It's something that Red Hat provides in their products only. > I'm

[EPEL-devel] Re: Adding the devtoolset repo for EPEL builds

2016-08-31 Thread Stephen John Smoogen
On 31 August 2016 at 04:58, dani wrote: > > > On 29/08//2016 22:23, Jason L Tibbitts III wrote: >>> >>> "d" == dani writes: >> >> d> I think it is high time to rethink the single version of a package >> d> policy, and come up with some scheme that

[EPEL-devel] Re: Adding the devtoolset repo for EPEL builds

2016-08-31 Thread dani
On 29/08//2016 22:23, Jason L Tibbitts III wrote: "d" == dani writes: d> I think it is high time to rethink the single version of a package d> policy, and come up with some scheme that would allow for any package d> to maintain multiple versions in a consistent manner.

[EPEL-devel] Re: Adding the devtoolset repo for EPEL builds

2016-08-29 Thread Jason L Tibbitts III
> "d" == dani writes: d> I think it is high time to rethink the single version of a package d> policy, and come up with some scheme that would allow for any package d> to maintain multiple versions in a consistent manner. We don't have such a policy. At least Fedora

[EPEL-devel] Re: Adding the devtoolset repo for EPEL builds

2016-08-27 Thread dani
On 27/08//2016 01:38, Neal Gompa wrote: On Fri, Aug 26, 2016 at 6:24 PM, dani wrote: I think it is high time to rethink the single version of a package policy, and come up with some scheme that would allow for any package to maintain

[EPEL-devel] Re: Adding the devtoolset repo for EPEL builds

2016-08-26 Thread Peter
On 16/08/16 06:24, Tom Callaway wrote: > I'd like to propose that we enable the Developer Toolset repo in EPEL > and allow packages to depend on it. Thoughts? There is one issue with this that I don't think others have addressed yet on this list. EPEL 6 supports i686 as a build target, but

[EPEL-devel] Re: Adding the devtoolset repo for EPEL builds

2016-08-26 Thread Neal Gompa
On Fri, Aug 26, 2016 at 6:24 PM, dani wrote: > > I think it is high time to rethink the single version of a package policy, > and come up with some scheme that would allow for any package to maintain > multiple versions in a consistent manner. We wouldn't even be the first

[EPEL-devel] Re: Adding the devtoolset repo for EPEL builds

2016-08-26 Thread Stephen John Smoogen
On 26 August 2016 at 12:58, Stephen John Smoogen wrote: > On 26 August 2016 at 06:00, Daniel Letai wrote: >> >> >> On 08/25/2016 11:40 PM, Kevin Fenzi wrote: >> >> Perhaps you could explain exactly what you want to propose here again? >> Just epel6? or 7 as

[EPEL-devel] Re: Adding the devtoolset repo for EPEL builds

2016-08-26 Thread Kevin Fenzi
On Thu, 25 Aug 2016 15:04:58 -0600 Dave Johansen wrote: > On Thu, Aug 25, 2016 at 2:34 PM, Kevin Fenzi wrote: > > > On Wed, 24 Aug 2016 21:59:55 -0600 > > Dave Johansen wrote: > > > > > I agree that how to handle SCLs can get

[EPEL-devel] Re: Adding the devtoolset repo for EPEL builds

2016-08-26 Thread Daniel Letai
On 08/25/2016 11:40 PM, Kevin Fenzi wrote: Perhaps you could explain exactly what you want to propose here again? Just epel6? or 7 as well? Do you have co-maintainers in case you get busy, etc? I propose adding several gnu packages (namely gcc, binutils and gdb) with versions following those

[EPEL-devel] Re: Adding the devtoolset repo for EPEL builds

2016-08-25 Thread Dave Johansen
On Thu, Aug 25, 2016 at 2:34 PM, Kevin Fenzi wrote: > On Wed, 24 Aug 2016 21:59:55 -0600 > Dave Johansen wrote: > > > I agree that how to handle SCLs can get really mess really fast, but > > a lot of projects are jumping on the "modern C++" bandwagon and

[EPEL-devel] Re: Adding the devtoolset repo for EPEL builds

2016-08-25 Thread Kevin Fenzi
On Thu, 25 Aug 2016 12:52:46 -0400 Stephen John Smoogen wrote: > On 25 August 2016 at 02:14, dani wrote: > > When I proposed importing gcc-5 to EPEL6 back in 04/2016 ( > >

[EPEL-devel] Re: Adding the devtoolset repo for EPEL builds

2016-08-25 Thread Kevin Fenzi
On Wed, 24 Aug 2016 21:59:55 -0600 Dave Johansen wrote: > I agree that how to handle SCLs can get really mess really fast, but > a lot of projects are jumping on the "modern C++" bandwagon and > allows devtoolset is low risk, easy to do and enables a lot of > packages to

[EPEL-devel] Re: Adding the devtoolset repo for EPEL builds

2016-08-25 Thread Stephen John Smoogen
On 25 August 2016 at 12:49, Stephen John Smoogen wrote: > On 24 August 2016 at 23:59, Dave Johansen wrote: >> On Wed, Aug 24, 2016 at 5:28 PM, Kevin Fenzi wrote: >> >> I agree that how to handle SCLs can get really mess really fast,

[EPEL-devel] Re: Adding the devtoolset repo for EPEL builds

2016-08-25 Thread Stephen John Smoogen
On 25 August 2016 at 02:14, dani wrote: > When I proposed importing gcc-5 to EPEL6 back in 04/2016 ( > https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org/message/F5JXEYPKQY77NRBCL4MNUBS3K2YYBBTU/ > ) the response was an unequivocal no, EPEL does

[EPEL-devel] Re: Adding the devtoolset repo for EPEL builds

2016-08-25 Thread Stephen John Smoogen
On 24 August 2016 at 23:59, Dave Johansen wrote: > On Wed, Aug 24, 2016 at 5:28 PM, Kevin Fenzi wrote: >> >> On Wed, 24 Aug 2016 16:43:31 -0600 >> Dave Johansen wrote: >> >> > On Wed, Aug 24, 2016 at 4:22 PM, Kevin Fenzi

[EPEL-devel] Re: Adding the devtoolset repo for EPEL builds

2016-08-25 Thread dani
When I proposed importing gcc-5 to EPEL6 back in 04/2016 ( https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org/message/F5JXEYPKQY77NRBCL4MNUBS3K2YYBBTU/ ) the response was an unequivocal no, EPEL does not install to /opt/ , so it dies right there. Now you are

[EPEL-devel] Re: Adding the devtoolset repo for EPEL builds

2016-08-24 Thread Dave Johansen
On Wed, Aug 24, 2016 at 5:28 PM, Kevin Fenzi wrote: > On Wed, 24 Aug 2016 16:43:31 -0600 > Dave Johansen wrote: > > > On Wed, Aug 24, 2016 at 4:22 PM, Kevin Fenzi wrote: > > > > > On Tue, 23 Aug 2016 14:21:24 +0100 > > > Karanbir Singh

[EPEL-devel] Re: Adding the devtoolset repo for EPEL builds

2016-08-24 Thread Kevin Fenzi
On Wed, 24 Aug 2016 16:43:31 -0600 Dave Johansen wrote: > On Wed, Aug 24, 2016 at 4:22 PM, Kevin Fenzi wrote: > > > On Tue, 23 Aug 2016 14:21:24 +0100 > > Karanbir Singh wrote: > > > > > On 22/08/16 18:30, Jason L Tibbitts III

[EPEL-devel] Re: Adding the devtoolset repo for EPEL builds

2016-08-24 Thread Dave Johansen
On Wed, Aug 24, 2016 at 4:22 PM, Kevin Fenzi wrote: > On Tue, 23 Aug 2016 14:21:24 +0100 > Karanbir Singh wrote: > > > On 22/08/16 18:30, Jason L Tibbitts III wrote: > > >> "DJ" == Dave Johansen writes: > > > > > > DJ>

[EPEL-devel] Re: Adding the devtoolset repo for EPEL builds

2016-08-24 Thread Kevin Fenzi
On Tue, 23 Aug 2016 14:21:24 +0100 Karanbir Singh wrote: > On 22/08/16 18:30, Jason L Tibbitts III wrote: > >> "DJ" == Dave Johansen writes: > > > > DJ> devtoolset is designed to do all of this and is already done, > > DJ> so it seems that

[EPEL-devel] Re: Adding the devtoolset repo for EPEL builds

2016-08-22 Thread Dave Johansen
On Mon, Aug 22, 2016 at 11:30 AM, Jason L Tibbitts III wrote: > > "DJ" == Dave Johansen writes: > > DJ> devtoolset is designed to do all of this and is already done, so it > DJ> seems that the only advantage to putting it in EPEL itself would be >

[EPEL-devel] Re: Adding the devtoolset repo for EPEL builds

2016-08-22 Thread Jason L Tibbitts III
> "DJ" == Dave Johansen writes: DJ> devtoolset is designed to do all of this and is already done, so it DJ> seems that the only advantage to putting it in EPEL itself would be DJ> to reduce the number of repos during build time. So is devtoolset something I get

[EPEL-devel] Re: Adding the devtoolset repo for EPEL builds

2016-08-16 Thread Dave Johansen
On Tue, Aug 16, 2016 at 11:07 AM, Kevin Fenzi wrote: > On Mon, 15 Aug 2016 14:24:21 -0400 > Tom Callaway wrote: > > > Recently, I've been participating in some discussion as to how to > > enable C++11 support for EPEL builds. Specifically, R (and its large

[EPEL-devel] Re: Adding the devtoolset repo for EPEL builds

2016-08-16 Thread Kevin Fenzi
On Mon, 15 Aug 2016 14:24:21 -0400 Tom Callaway wrote: > Recently, I've been participating in some discussion as to how to > enable C++11 support for EPEL builds. Specifically, R (and its large > universe of addons in CRAN) would benefit significantly from C++11 > support. >

[EPEL-devel] Re: Adding the devtoolset repo for EPEL builds

2016-08-15 Thread Neal Gompa
On Mon, Aug 15, 2016 at 2:40 PM, Dave Johansen wrote: > On Mon, Aug 15, 2016 at 12:24 PM, Tom Callaway wrote: >> >> Recently, I've been participating in some discussion as to how to enable >> C++11 support for EPEL builds. Specifically, R (and its

[EPEL-devel] Re: Adding the devtoolset repo for EPEL builds

2016-08-15 Thread Dave Johansen
On Mon, Aug 15, 2016 at 12:24 PM, Tom Callaway wrote: > Recently, I've been participating in some discussion as to how to enable > C++11 support for EPEL builds. Specifically, R (and its large universe > of addons in CRAN) would benefit significantly from C++11 support. > >