[gentoo-dev] Re: The state and future of the OpenRC project

2014-06-09 Thread Duncan
William Hubbs posted on Mon, 09 Jun 2014 22:14:34 -0500 as excerpted: > Daniel Robbins assisted me today with tweaking the bios of the box I > plan to put Gentoo on so that I can boot it from a cdrom. Also he > alerted me to this thread, so that is why I wanted to post this update. > > He will al

Re: [gentoo-dev] Re: The state and future of the OpenRC project

2014-06-09 Thread William Hubbs
All, I attempted to post an update a bit earlier, but I haven't seen it yet, so I thought I would try again. Thanks to Daniel Robbins of funtoo, I am about to getGentoo installed on another box, so I will be able to take the lead on OpenRC again. He assisted me on Skype today with getting in

[gentoo-dev] Re: [RFC] News item: GCC 4.8.3 defaults to -fstack-protector

2014-06-09 Thread Ryan Hill
On Tue, 10 Jun 2014 04:31:27 +0200 Jeroen Roovers wrote: > On Mon, 9 Jun 2014 18:16:02 -0600 > Ryan Hill wrote: > > > Beginning with GCC 4.8.3, Stack Smashing Protection (SSP) will be > > enabled by default.[..] > > .. on supported architectures. > > > Right? Yes. But now you've got me wor

Re: [gentoo-dev] The state and future of the OpenRC project

2014-06-09 Thread William Hubbs
All, just a quick update. I now have a box set up for installing gentoo on it so I will be able to take the lead on OpenRC again. I will have that up and running, probably tomorrow, then I also have a medical situation I have to take care of in a couple of weeks. I will continue to be inte

Re: [gentoo-dev] Re: The state and future of the OpenRC project

2014-06-09 Thread heroxbd
Alexey Shvetsov writes: > However this will depend on migration of gentoo-x86 to git Well, we can start evaluating gitlab for git overlays and gentoo hosted projects, such as (back to topic :) OpenRC. Is the infra team interested in this option? pgpqPDX0LzcUz.pgp Description: PGP signature

Re: [gentoo-dev] [RFC] News item: GCC 4.8.3 defaults to -fstack-protector

2014-06-09 Thread Jeroen Roovers
On Mon, 9 Jun 2014 18:16:02 -0600 Ryan Hill wrote: > Beginning with GCC 4.8.3, Stack Smashing Protection (SSP) will be > enabled by default.[..] .. on supported architectures. Right? jer

Re: [gentoo-dev] The state and future of the OpenRC project

2014-06-09 Thread heroxbd
Alexander Berntsen writes: > It would be cool if some of the OpenRC hackers had the time to set up > a developer's wiki or similar, where they share their workflow and > similar. Nice idea, on my list. pgp5kJikw7nfi.pgp Description: PGP signature

[gentoo-dev] [RFC] News item: GCC 4.8.3 defaults to -fstack-protector

2014-06-09 Thread Ryan Hill
Title: GCC 4.8.3 defaults to -fstack-protector Author: Ryan Hill Content-Type: text/plain Posted: 2014-06-10 Revision: 1 News-Item-Format: 1.0 Display-If-Installed: >=sys-devel/gcc-4.8.3 Beginning with GCC 4.8.3, Stack Smashing Protection (SSP) will be enabled by default. The 4.8 series will ena

Re: [gentoo-dev] The state and future of the OpenRC project

2014-06-09 Thread Tom Wijsman
On Mon, 09 Jun 2014 21:45:26 + hasufell wrote: > Probably because no one mentored them on how to fix these QA issues. > Otherwise... if that's attitude, then that's just sad and has to be > fixed by those who run that overlay (review, contribution guidelines). > > And I still think that the

Re: [gentoo-dev] The state and future of the OpenRC project

2014-06-09 Thread hasufell
Thomas Kahle: > then they stay in the overlay > because people feel it is not worth the effort to fix the QA > issues which in turn would be necessary before moving them to the > main tree. > Probably because no one mentored them on how to fix these QA issues. Otherwise... if that's attitude, the

[gentoo-dev] New eclass: gstreamer.eclass (replacement for gst-plugins*.eclass)

2014-06-09 Thread Michał Górny
Hello, For some time I've been working on bringing multilib gstreamer into the tree. Following recent review by gstreamer team, I would like to submit the new eclass for a wider opinion. The gstreamer.eclass intends to replace all of gst-plugins* eclasses. It provides routines suitable for buildi

Re: [gentoo-dev] The state and future of the OpenRC project

2014-06-09 Thread Thomas Kahle
On 08/06/14 18:06, hasufell wrote: > I am not sure if that is a joke. You can pretty much ask most major > gentoo projects. The ones where I was involved more deeply definitely > suffer from that problem, including sunrise and games team. Science team > gave up importing major ebuilds to the tree a

Re: [gentoo-dev] Packages up for grabs

2014-06-09 Thread Mikle Kolyada
09.06.2014 21:47, Jeroen Roovers пишет: > On Mon, 09 Jun 2014 21:34:06 +0400 > Mikle Kolyada wrote: > >>> app-admin/389-admin-console >>> app-admin/389-console >>> app-admin/389-ds-console >>> app-admin/aws-as-tools >>> app-admin/aws-elb-tools >>> app-admin/aws-iam-tools >>> app-admin/aws-rds-too

Re: [gentoo-dev] Packages up for grabs

2014-06-09 Thread Jeroen Roovers
On Mon, 09 Jun 2014 21:34:06 +0400 Mikle Kolyada wrote: > > app-admin/389-admin-console > > app-admin/389-console > > app-admin/389-ds-console > > app-admin/aws-as-tools > > app-admin/aws-elb-tools > > app-admin/aws-iam-tools > > app-admin/aws-rds-tools > > app-emulation/edumips64 > > dev-java/id

Re: [gentoo-dev] Packages up for grabs

2014-06-09 Thread Mikle Kolyada
08.06.2014 16:25, Fabio Erculiani пишет: > Due to permanent lack of time, I'm unable to properly maintain the > packages below. > Feel free to take them over. I'll remove myself from metadata.xml in 14 days. > > app-admin/389-admin-console > app-admin/389-console > app-admin/389-ds-console > app-a

Re: [gentoo-dev] Re: The state and future of the OpenRC project

2014-06-09 Thread Amadeusz Żołnowski
Rich Freeman writes: > Uh, you can't force anybody to do anything, and most of them are no > longer around. You can always encourage or ask nicely. Yes, I meant that: forcing by asking nicely. :-) > You can also set a policy of no further commits accepted without > accompanying documentation,

Re: [gentoo-dev] Re: The state and future of the OpenRC project

2014-06-09 Thread Rich Freeman
On Mon, Jun 9, 2014 at 4:57 AM, Amadeusz Żołnowski wrote: > > We should focus on forcing people who were involved into OpenRC to > document what they know. Uh, you can't force anybody to do anything, and most of them are no longer around. You can always encourage or ask nicely. You can also set

Re: [gentoo-dev] Re: The state and future of the OpenRC project

2014-06-09 Thread Amadeusz Żołnowski
Michael Palimaka writes: > Perhaps we could consider GitLab? +1 on that. I have deployed it recently at work and it seems to perform well. *Really* easy to use. Easy to deploy as well. It's written in Ruby, *not Java*. It's possible to have a basic integartion with external issue trackers.