On 3/16/22 18:01, Jakov Smolić wrote:
# Jakov Smolić (2022-03-16)
# -only ebuilds, various other QA issues (no python
# 3.10, using deprecated EAPI, ...)
# Removal on 2022-04-15.
net-libs/libmirisdr
media-sound/deinvert
net-wireless/gr-m2k
adding net-wireless/libm2k as well. This package wa
On 02/19/15 06:38, Alexis Ballier wrote:
> On Thu, 19 Feb 2015 19:34:28 +0800
> Patrick Lauer wrote:
>
>> On Thursday 19 February 2015 12:31:27 Alexis Ballier wrote:
>>> On Wed, 18 Feb 2015 22:48:27 +0100
>>>
>>> Michał Górny wrote:
Dnia 2015-02-18, o godz. 16:11:53
"Mike Frysinge
On 11/04/2014 08:16 PM, Michael Orlitzky wrote:
> When I was taking my ebuild quizzes, I asked for someone to clarify the
> implicit system dependency that we have enshrined in the devmanual:
>
> https://bugs.gentoo.org/show_bug.cgi?id=485356
>
> There is... some agreement, but also special cas
On 11/01/2014 03:36 PM, Sven Vermeulen wrote:
> On Sat, Nov 01, 2014 at 01:52:57PM +0100, Michał Górny wrote:
>>> Michał Górny told me on IRC that I might be approaching this incorrectly (or
>>> at least, inefficiently). I was working on the massive bug-spree (right now
>>> stopped around 22% of th
On 10/12/2014 02:03 PM, Dan Douglas wrote:
> On Sun, Oct 12, 2014 at 11:22 AM, Anthony G. Basile
> wrote:
>> --- toolchain-funcs.eclass.orig2014-10-12 11:23:41.585182742 -0400
>> +++ toolchain-funcs.eclass2014-10-12 11:31:57.170205300 -0400
>> @@ -610,6 +610,12 @@
>> directive=$(gcc-
On 10/05/2014 06:44 PM, Ryan Hill wrote:
> Hey all, I'm stepping down as GCC maintainer. I haven't been reading
> toolchain
> bugmail since June, and keep telling myself I'll tackle it next weekend, which
> never happens. To be frank, I'm kinda sick of Gentoo. I'm hoping it's
> temporary but we
On 09/17/2014 09:58 AM, Rich Freeman wrote:
> There was a thread a while back about mix-in support and I think there
> was genuine interest. For the most part we just need to do the work,
> and the first step is identifying blockers. If some end up involving
> PMS/etc then we may need to get the
On 09/07/2014 09:03 PM, Rich Freeman wrote:
> Right now the general policy is that we don't allow unmasked (hard or
> via keywords) ebuilds in the tree if they use an scm to fetch their
> sources. There are a bunch of reasons for this, and for the most part
> they make sense.
Hard masking is a re
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/26/2014 06:23 PM, Anthony G. Basile wrote:
> On 08/26/14 17:00, Alexander Tsoy wrote:
>> On Tue Aug 26 22:27:36 2014 Anthony G. Basile
>> wrote:
>>> Hi everyone,
>>>
>>> I plan to update the pax-utils.eclass because of bug #520198. Can
>>> peo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- -BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/27/2014 09:55 AM, Pacho Ramos wrote:
> Today some user on IRC noted that there were some doubts about if
> developers are allowed to stabilize packages they maintain when they are
> able to test on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/21/2014 06:52 PM, William Hubbs wrote:
> I'm picking a random msg to reply to.
>
> My concern about doing a revbump just because the deps change is that
> the new revision has to be committed in ~arch, so we then have to hit
> the arch teams, wh
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/08/2014 09:48 PM, Matthew Thode wrote:
> arm has a historical problem with stabilization, while keywording
> doesn't require access to all arm sub-arches the problem with the
> stabilization slowness causes running a full ~arm to become hard. By
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/04/2014 12:25 PM, dREPLACEeLETTEReEjBYeLETTEReAatGMA ILcom wrote:
It is incredibly hard to seriously review anything with this from email
address.
- -Zero
> Hello to all,
>
> Summary: I have made many mods to sys-app/portage (2013 version).
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/02/2014 03:07 PM, Anthony G. Basile wrote:
> On 07/02/14 14:41, Rick "Zero_Chaos" Farina wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> On 07/02/2014 02:10 PM, Rich Freeman wrote:
>&
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/02/2014 02:10 PM, Rich Freeman wrote:
> On Wed, Jul 2, 2014 at 1:54 PM, Michał Górny wrote:
>> I don't feel like we ought to vote on something like this without
>> understanding most of the current profiles. And I'm afraid there are
>> only few
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/07/2014 04:59 PM, Anthony G. Basile wrote:
> Related to this, I'd like to take care of sys-apps/gentoo-functions in
> WilliamH's absence. There's a couple of items to fix and I'd like to
> get them done. Any objections?
>
Knowing WilliamH fa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/30/2014 01:39 PM, Fabio Erculiani wrote:
> configs should have never gotten into genkernel in the first place.
> it's each kernel pkg (or even version) that owns a valid config of
> itself.
> I am part of genkernel@ but I have no will nor time to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/30/2014 11:10 AM, Samuli Suominen wrote:
> I can't find anyone with access that actually replies to mails, pings,
> ... to genkernel repository for:
>
> https://bugs.gentoo.org/show_bug.cgi?id=461828
>
> I'll p.mask it on amd64 profiles if noon
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/23/2014 03:42 PM, Rémi Cardona wrote:
> Le vendredi 23 mai 2014 à 22:57 +0700, gro...@gentoo.org a écrit :
>> # Google closed free usage of the translate api
>> # Masked for removal in 30 days
>> app-text/qgoogletranslator
>>
>> # openmcl has bee
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/12/2014 01:08 PM, Michał Górny wrote:
> Dnia 2014-05-12, o godz. 12:07:11
> "Rick \"Zero_Chaos\" Farina" napisał(a):
>
>> What about talking to local network resources? In my metasploit ebuild
>> it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/11/2014 05:42 PM, Michał Górny wrote:
> Hi, everyone.
>
> Almost 9 months ago I've committed three new FEATURES for portage:
> cgroup, ipc-sandbox and network-sandbox. Today I'd like to propose
> enabling at least the latter two by default.
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/14/2014 04:35 AM, Alice Ferrazzi wrote:
>> There are a list of packages up for grabs. I cannnot test anymore some of
>> them, or i stopped use them.
>>
>> app-text/fbreader
>> dev-libs/liblinebreak
>> net-wireless/madwimax
>> net-wireless/wimax-t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I forgot to send this out when I originally masked the package so the 30
days will start now.
# Rick Farina (22 Mar 2014)
# Upstream has replaced dev-util/dissy with dev-util/emilpro
# Please switch to emilpro or report issues in bug #505380
# remova
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/08/2014 02:40 PM, Mike Gilbert wrote:
Gentoo typically tries to keep patching to a minimum in general. To be
enabling something like this by default seems bad, the fact that it is
openssh compounds that. +1 for removing the + and leaving this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/02/2014 02:22 PM, Mike Gilbert wrote:
> On Wed, Apr 2, 2014 at 12:52 PM, Samuli Suominen wrote:
>> The "30 days maintainer time out" stabilization policy isn't working
>> when package has multiple SLOTs, because
>> the bugs are filed for only la
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/10/2014 07:29 PM, Gilles Dartiguelongue wrote:
> Picking a random mail in the thread.
>
> Making udev dependency always on is a deliberate choice here, as noted
> by Alexandre, the library will be most likely useless without it and we
> simply d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/24/2014 12:32 AM, Samuli Suominen wrote:
> If it's okay, I'd want to post this fast, before adding KEYWORDS to
> sys-fs/udev-209's ebuild
>
>
Should means required now? Man if I only knew that last week...
- -Zero
-BEGIN PGP SIGNATURE-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/02/2014 02:00 AM, Samuli Suominen wrote:
>
> On 02/04/14 05:02, Matt Turner wrote:
>> On Tue, Apr 1, 2014 at 9:38 AM, Tom Wijsman wrote:
>>> Projects like the Council, ComRel and QA are there to protect Gentoo;
>>> and yes, people are (or shoul
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/01/2014 02:41 PM, Samuli Suominen wrote:
>
> On 01/04/14 21:33, Tom Wijsman wrote:
>> Okay, but this isn't what happened yet; because your plan was to send
>> out a mail after stabilization for everyone to adapt the reverse
>> dependencies, and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/01/2014 11:55 AM, Samuli Suominen wrote:
>
> On 01/04/14 18:28, Tom Wijsman wrote:
>> On Tue, 01 Apr 2014 12:23:43 +
>> hasufell wrote:
>>
>>> And this is going to get worse if people don't trust them. Currently
>>> it looks more like a loo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/31/2014 01:50 AM, Samuli Suominen wrote:
>
> On 30/03/14 23:45, Rick "Zero_Chaos" Farina wrote:
>>
>> Your input will be considered here with all the weight it deserves. My
>> mask was to force this discussio
n the list and it has done it's job well.
Thanks,
Zero
>
>
> On 28/03/14 23:48, Rick "Zero_Chaos" Farina wrote:
>> Recently, without discussion as suggested by the dev manual, new
>> virtuals were added for libudev and libgudev.
>>
>> These virtua
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Recently, without discussion as suggested by the dev manual, new
virtuals were added for libudev and libgudev.
These virtuals are different than any virtuals use in gentoo in the
past, and due to this, I fell the discussion step is critical. As such,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/31/2013 06:43 PM, Andreas K. Huettel wrote:
> Am Dienstag, 31. Dezember 2013, 23:30:14 schrieb Mike Gilbert:
>> I have noticed that the arch profile directories (profiles/arch/$ARCH)
>> are not EAPI 5 capable. These profiles are inherited by both
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/07/2014 06:00 PM, Denis Dupeyron wrote:
> On Wed, Feb 5, 2014 at 11:30 PM, Canek Peláez Valdés wrote:
>> Hi. TL;DR, this is basically just a THANK YOU to the Gentoo devs
>
> This is totally unacceptable. I demand you take your thank-yous back.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/05/2014 07:48 PM, Tom Wijsman wrote:
> On Wed, 05 Feb 2014 17:05:08 -0500
> "Rick \"Zero_Chaos\" Farina" wrote:
>
>>>
>>> Yes, making the newest versions never available because the old
>>&
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/05/2014 04:48 PM, Tom Wijsman wrote:
> On Wed, 05 Feb 2014 10:07:22 -0600
> Steev Klimaszewski wrote:
>
>> Against my better judgment...
>>
>> On Wed, 2014-02-05 at 05:55 +0100, Tom Wijsman wrote:
>>> On Tue, 04 Feb 2014 21:15:47 -0600
>>> Stee
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/01/2014 01:42 PM, Rich Freeman wrote:
> On Sat, Feb 1, 2014 at 12:35 PM, Rick "Zero_Chaos" Farina
> wrote:
>>
>> I see exactly zero downside to doing this, so if whoever is going to
>> actually do the editing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/01/2014 10:06 AM, Andreas K. Huettel wrote:
>
> Dear all,
>
> in its last session the Gentoo council decided that 30 days from now the
> entire profile tree will be updated to require EAPI=5 support.
>
> For all non-deprecated profiles this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/10/2014 10:50 AM, Ryan Hill wrote:
> On Fri, 10 Jan 2014 01:35:09 -0500
> "Rick \"Zero_Chaos\" Farina" wrote:
>
>> More to the point, "this specific use flag" appears to have no purpose
>> wh
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/09/2014 07:17 PM, Ryan Hill wrote:
> On Thu, 9 Jan 2014 17:30:46 -0600 Ryan Hill
> wrote:
>
>> On Thu, 09 Jan 2014 17:29:26 -0500 "Rick \"Zero_Chaos\" Farina"
>> wrote:
>>
>>> -BE
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/09/2014 07:12 PM, Ryan Hill wrote:
> On Thu, 9 Jan 2014 17:41:08 -0600
> William Hubbs wrote:
>
>> On Fri, Jan 10, 2014 at 12:30:04AM +0100, Andreas K. Huettel wrote:
>>> Am Freitag, 10. Januar 2014, 00:26:03 schrieb Ryan Hill:
> Pleas
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/09/2014 06:09 PM, Anthony G. Basile wrote:
> On 01/09/2014 05:29 PM, Rick "Zero_Chaos" Farina wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> On 01/09/2014 05:21 PM, Michał Górny wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/09/2014 06:01 PM, Anthony G. Basile wrote:
> On 01/09/2014 05:21 PM, Michał Górny wrote:
>> Dnia 2014-01-09, o godz. 17:06:52
>> "Anthony G. Basile" napisał(a):
>>
>>> On 01/09/2014 04:57 PM, Pacho Ramos wrote:
What are the advantages of di
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/09/2014 05:21 PM, Michał Górny wrote:
> Dnia 2014-01-09, o godz. 17:06:52
> "Anthony G. Basile" napisał(a):
>
>> On 01/09/2014 04:57 PM, Pacho Ramos wrote:
>>> What are the advantages of disabling SSP to deserve that "special"
>>> handling via
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/09/2014 03:58 PM, Magnus Granberg wrote:
> Hi
>
> Some time ago we discussed that we should enable stack smashing
> (-fstack-protector) by default. So we opened a bug to track this [1].
> The affected Gcc version will be 4.8.2 and newer. Onl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/08/2014 03:27 PM, Robin H. Johnson wrote:
> On Wed, Jan 08, 2014 at 09:14:43PM +0100, Peter Stuge wrote:
>> Robin H. Johnson wrote:
>>> Comments:
>>> -
>>> In bug #4411, comment 43, vapier noted:
any package that does dlopen("libfoo.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/01/2014 09:40 PM, Michael Orlitzky wrote:
> On 01/01/2014 09:13 PM, Rick "Zero_Chaos" Farina wrote:
>>
>>> What use case is there for having the LICENSE apply to anything else?
>>
>> Some of us do redis
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/01/2014 08:51 PM, Michael Orlitzky wrote:
> On 01/01/2014 05:28 PM, Ulrich Mueller wrote:
>> Hi,
>> According to GLEP 23 [1], the LICENSE variable regulates the software
>> that is installed on a system. There is however some ambiguity in
>> this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/01/2014 05:28 PM, Ulrich Mueller wrote:
> Hi, According to GLEP 23 [1], the LICENSE variable regulates the
> software that is installed on a system. There is however some
> ambiguity in this: should it cover the actual files installed on
> the sy
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/30/2013 03:48 PM, Emery Hemingway wrote:
> I really like working with Go, and would like to see a means of merging
> Go packages with Portage. In short I am asking if anyone else is
> interested in a Go project.
>
>
> For those who aren't famil
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/14/2013 07:59 PM, William Hubbs wrote:
> You make some good points. I'll answer your questions as best as I can,
> but we can consider this thread closed. I will not try to put the
> virtual in, but I will come back to the list soon and start ano
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/15/2013 07:20 PM, Andreas K. Huettel wrote:
> Am Montag, 16. Dezember 2013, 00:34:13 schrieb Matt Turner:
>> 3dnow: Use the 3DNow! instruction set
>> 3dnowext: Use the Enhanced 3DNow! instruction set
>> mmx: Use the MMX instruction set
>> mmxext:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/14/2013 04:57 PM, William Hubbs wrote:
> On Sat, Dec 14, 2013 at 08:47:01PM +, Jorge Manuel B. S. Vicetto wrote:
>> OK, I see what you mean.
>> To be clear, I'm not ready to have a stage3 without netifrc. If / when we
>> update catalyst so t
gt; Let me try my post again, with a bit more quoting:
>>
>> On Mon, Dec 9, 2013 at 2:56 PM, Rick "Zero_Chaos" Farina
>> wrote:
>>> What if he wants to
>>> put a stage3 on a disk for his amd64 box from his arm box? I'd love to
>>> see him
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/09/2013 10:28 AM, Rich Freeman wrote:
> On Mon, Dec 9, 2013 at 9:50 AM, Rick "Zero_Chaos" Farina
> wrote:
>> I can honestly say most of the time when setup my arm systems I'm
>> unpacking the arm stage3 on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/08/2013 05:25 PM, William Hubbs wrote:
> On Sat, Dec 07, 2013 at 12:52:08AM -0500, Rick "Zero_Chaos" Farina wrote:
>> 1.) If we are going to stuff this into @system then we probably want a
>> USE=nonet flag to allow user
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/07/2013 07:42 AM, Rich Freeman wrote:
>> Honestly, I'm not really sure why anyone would want to make stage3 less
>> functional than it already is but honestly net isn't something I'm ready
>> to give up just yet.
>
> It isn't about making the st
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/03/2013 04:11 PM, William Hubbs wrote:
> I would like to add a virtual/network-manager package to @system which
> has the following rdepend settings:
>
> RDEPEND=" || (
> net-misc/netifrc
> >=sys-apps/openrc-0.12[newnet]
> net-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/02/2013 03:28 PM, William Hubbs wrote:
> On Sun, Dec 01, 2013 at 11:20:15AM +0100, Alessandro DE LAURENZIS wrote:
>
> *snip*
>
>> The other two cases need a clarification:
>> 3) -netifrc -newnet: no network stack?!?
>
> That's correct, you do
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/24/2013 12:28 PM, Anthony G. Basile wrote:
> Hi everyone,
>
> I'd like to bounce a question of the community regarding the order of
> profile stackings. We have a suggestion in hardened to re-introduce the
> hardened desktop profile. This was
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/16/2013 10:28 AM, Anthony G. Basile wrote:
> On 11/16/2013 04:11 AM, Ulrich Mueller wrote:
>>> On Fri, 15 Nov 2013, Robin H Johnson wrote:
>>> Add this line to the dev-lang/python-exec ebuilds:
>>> PDEPEND=">=dev-python/python-exec-1:$SLO
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/13/2013 01:58 PM, Francesco R. wrote:
>
> long story short having a portage-20130126.tar.bz2 snapshot
> (before the EAPI 5 switch) greatly simplified the upgrade of an old
> server on a client.
>
> Why not keep a copy on the servers? I mean
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/02/2013 06:09 PM, yac wrote:
> On Sat, 02 Nov 2013 16:57:07 -0400
> "Rick \"Zero_Chaos\" Farina" wrote:
>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>
>> On 11/02/2013 04:35 PM,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/02/2013 04:35 PM, yac wrote:
> On Sat, 02 Nov 2013 15:20:41 -0400
> "Rick \"Zero_Chaos\" Farina" wrote:
>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>
>> On 11/02/2013 11:03 AM, Mich
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/02/2013 11:03 AM, Michał Górny wrote:
> Dnia 2013-11-02, o godz. 14:51:26
> Tom Wijsman napisał(a):
>
>> On Sat, 02 Nov 2013 09:16:45 -0400
>> "Anthony G. Basile" wrote:
>>
>>> This is a followup to a discussion on IRC yesterday regarding
>>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> net-analyzer/sslsniff #zerochaos seems to have this as well, I can
> co-maintain :D
be my guest
- -Zero
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBAgAGB
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/15/2013 07:29 PM, Vicente Olivert Riera wrote:
> Can't the users download and install those tables manually from the
> official ophcrack website/server? If so, maybe adding the instructions
> in the pkg_postinst() phase of app-crypt/ophcrack ebui
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/11/2013 12:07 PM, Jeroen Roovers wrote:
> On Fri, 11 Oct 2013 18:00:33 +0200
> hasufell wrote:
>> I c. Woukd there be a way to change the plugin dir, so it is not
>> version specific anymore?
>
> Yes, we could call wireshark's configure with
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/11/2013 11:42 AM, hasufell wrote:
> On 01/30/2013 05:28 AM, Richard Farina (zerochaos) wrote:
>> zerochaos13/01/30 04:28:06
> [...]
>
>> LICENSE="GPL-2" -SLOT="0" +SLOT="0/${PV}" KEYWORDS="~alpha ~amd64
>> ~arm ~hppa ~ia64 ~ppc ~ppc64 ~sparc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/28/2013 10:12 PM, hero...@gentoo.org wrote:
> "Rick \"Zero_Chaos\" Farina" writes:
>
>> On 09/28/2013 03:00 AM, Ulrich Mueller wrote:
>>>>>>>> On Sat, 28 Sep 2013, heroxbd wrot
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/28/2013 03:00 AM, Ulrich Mueller wrote:
>> On Sat, 28 Sep 2013, heroxbd wrote:
>
>> I am revisiting this topic based on previous discussions[1,2,3].
>
>> There seems to be a constant need for toolchain with a new EAPI. The
>> only block is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/23/2013 04:41 PM, Markos Chandras wrote:
> On 09/23/2013 09:31 PM, Alexis Ballier wrote:
>> On Mon, 23 Sep 2013 22:03:49 +0200
>> Agostino Sarubbo wrote:
>>
>>> Hello,
>>>
>>> the council has decided[1] to drop m68k, sh, s390 to unstable. If
>>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/21/2013 08:44 AM, Pacho Ramos wrote:
> El sáb, 21-09-2013 a las 14:42 +0200, Pacho Ramos escribió:
>> I don't have time for it for a long time (since I switched to official
>> suspend time ago and moved back to gentoo-sources then), updated patch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/07/2013 05:11 PM, Ryan Hill wrote:
> On Sat, 7 Sep 2013 18:10:42 + (UTC)
> Martin Vaeth wrote:
>
>> Ryan Hill wrote:
>>>
>>> * -fstack-protector{-all}
>>> No thank you. -fstack-protector has very limited coverage
>>
>> I'd say it covers m
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/07/2013 01:25 PM, Ryan Hill wrote:
> On Thu, 05 Sep 2013 12:13:28 +0200
> Agostino Sarubbo wrote:
>
>> Hello,
>>
>> during an irc debate, me and other people just noticed that the default
>> profile could use more flags to enhance the security
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/05/2013 07:06 AM, Mike Frysinger wrote:
> On Thursday 05 September 2013 06:13:28 Agostino Sarubbo wrote:
>> during an irc debate, me and other people just noticed that the default
>> profile could use more flags to enhance the security.
>>
>> An
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> ozzie src # emerge -vp ruby
>
>
> These are the packages that would be merged, in reverse order:
>
> Calculating dependencies... done!
>
> emerge: there are no ebuilds built with USE flags to satisfy
> ">=dev-ruby/rake-0.9.6[ruby_targets_ruby20]"
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/22/2013 07:24 AM, Rich Freeman wrote:
> On Thu, Aug 22, 2013 at 6:19 AM, Markos Chandras wrote:
>> On 22 August 2013 11:01, Rich Freeman wrote:
>>> I think the result of a policy like this would be that stable keywords
>>> would get dropped on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/31/2013 03:57 PM, Tom Wijsman wrote:
> On Sat, 31 Aug 2013 20:45:00 +0200
> Pacho Ramos wrote:
>
>> El sáb, 31-08-2013 a las 12:37 -0400, Rick "Zero_Chaos" Farina
>> escribió: [...]
>>> I know we ar
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/31/2013 01:29 PM, Jeroen Roovers wrote:
> On Sat, 31 Aug 2013 12:37:58 -0400
> "Rick \"Zero_Chaos\" Farina" wrote:
>
>> I know we are a little OT here but the fifth type of recruit is
>
> Yes.
>
&g
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/21/2013 05:13 AM, Tom Wijsman wrote:
> On Wed, 21 Aug 2013 12:32:35 +0400
> Sergey Popov wrote:
>
>> 21.08.2013 12:13, Tom Wijsman пишет:
>>> Recruiting shows to be a hard task; so, the suggestions I am doing
>>> are assuming that that doesn't
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/30/2013 07:37 PM, Michał Górny wrote:
> Hello, all.
>
> After a few days of thinking, discovering and working, here it is.
> The first working draft of new git eclass codenamed 'git-r3'.
>
> First of all, the name is not final. I'm open to idea
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> The new eclass is supposedly used by 732 in-tree packages [1],
> and possibly a few dozens out-of-the-tree. Some parts of the eclass API
> are barely used. I would really prefer to avoid yet another eclass
> migration.
that's a shame, I don't think
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/20/2013 06:26 AM, Michał Górny wrote:
> Hello, fellow developers.
>
> I've added a few new fancy features for Gentoo developers to portage
> git. Sadly, since Zac isn't planning another release until 2.2.0 goes
> stable, you need to switch to -9
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/18/2013 12:39 PM, Ulrich Mueller wrote:
> Hi all,
>
> For EAPI 6, introduction of a patch applying function to the package
> manager itself is being discussed. This would serve two purposes:
> - support for PATCHES variable in a default src_inst
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/13/2013 01:21 AM, heroxbd wrote:
> Dear Fellows,
>
> Canonical is raising money by pushing their concept of Ubuntu for
> Android[1][2]. The idea is to put GNU environment (esp. Ubuntu userland)
> in parallel to Android to drive the external HDMI
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/11/2013 04:30 PM, Michał Górny wrote:
> Dnia 2013-08-11, o godz. 20:59:01
> Tom Wijsman napisał(a):
>
>> On Sun, 11 Aug 2013 13:29:16 -0500
>> William Hubbs wrote:
>>
>>> I am splitting this to a separate thread, because it could become a
>>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/27/2013 12:08 AM, Matt Turner wrote:
> (I sent this to gentoo-releng@. Resending to gentoo-dev@ for a wider audience)
>
> Can we make autobuilds go to /experimental and then only move them to
> /releases when someone actually tests them?
>
> Lo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/25/2013 01:28 PM, Zac Medico wrote:
> On 07/25/2013 08:29 AM, Rick "Zero_Chaos" Farina wrote:
>>>> Shall we revisit that, and try to make portage behave more correctly,
>>>> even if it means more r
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
>> Shall we revisit that, and try to make portage behave more correctly,
>> even if it means more revbumps / rebuilding?
>
> Just set EMERGE_DEFAULT_DEPS="--dynamic-deps=n" in make.conf if you'd
> like to test it.
>
>
What (if anything) does that br
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/24/2013 03:18 PM, Ciaran McCreesh wrote:
> On Wed, 24 Jul 2013 21:17:26 +0200
> Michał Górny wrote:
>> Other thing is that Portage explicitly ignores PMS in this matter
>> and uses dependencies from ebuilds rather than recorded ones. This is
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/23/2013 03:37 PM, Roy Bamford wrote:
> On 2013.07.23 01:57, Rick "Zero_Chaos" Farina wrote:
> [snip]
>
>> I think the real difference [between the foundation and council] is
>> that most of the devs don't
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/22/2013 07:05 PM, Rich Freeman wrote:
> On Mon, Jul 22, 2013 at 6:35 PM, Rick "Zero_Chaos" Farina
> wrote:
>> The council really doesn't have the ability to just instantly vote on
>> things outside of a meeti
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/22/2013 05:51 PM, Rich Freeman wrote:
> On Sun, Jul 21, 2013 at 4:20 PM, Roy Bamford wrote:
>>> - vote for holding meetings every 2nd Tuesday of the month at 2000
>>> UTC
>>> (or
>>> 1900 UTC depending on daylight savings)
>>
>> In any timezone
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/17/2013 05:47 PM, hasufell wrote:
> On 07/17/2013 11:42 PM, Rick "Zero_Chaos" Farina wrote:
>> On 07/17/2013 05:34 PM, hasufell wrote:
>>> On 07/17/2013 11:28 PM, Rick "Zero_Chaos" Farina wrote:
>>&g
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/17/2013 05:34 PM, hasufell wrote:
> On 07/17/2013 11:28 PM, Rick "Zero_Chaos" Farina wrote:
>> On 07/17/2013 05:17 PM, Chris Reffett wrote:
>>> On 07/17/2013 04:57 PM, hasufell wrote:
>>>> I know ther
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/17/2013 05:17 PM, Chris Reffett wrote:
> On 07/17/2013 04:57 PM, hasufell wrote:
>> I know there was an announcement about the upcoming change to
>> cmake-utils.eclass, however... it is not enough to give a deadline
>> without caring if people
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/10/2013 10:03 PM, Robin H. Johnson wrote:
> On Fri, Jul 05, 2013 at 09:27:46PM -0700, Brian Dolbec wrote:
>> The other thing we needed to do was completely remove the use of
>> or building of binpkgs during the update_seed stage. Portage has
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/06/2013 03:08 AM, Matt Turner wrote:
> On Fri, Jul 5, 2013 at 7:18 PM, Rick "Zero_Chaos" Farina
> wrote:
>> When we then move onto stage 2, it uses just the packages built during
>> stage1 (/tmp/stage1root becomes /)
1 - 100 of 227 matches
Mail list logo
