Just a heads up for everybody. You might see some minor blips in
www.gentoo.org service tonight, while I'm switching it to other hosting
so that I can do heavy maintenance on the existing www boxes.
--
Robin Hugh Johnson
Gentoo Linux Developer & Infra Guy
E-Mail : [EMAIL PROTECTED]
GnuPG FP
On Monday, November 3, 2008 02:22:12 Peter Volkov wrote:
> В Вск, 02/11/2008 в 12:11 -0700, Gordon Malm пишет:
> > You can cry "abuse" all you want. You FAIL to offer any alternatives or
> > solutions. I'll ask again, how do you detect that you are compiling code
> > destined to be run in-kernel
On Tue, Nov 04, 2008 at 02:00:27AM -0100, Jorge Manuel B. S. Vicetto wrote:
> media-libs/libexiferadicator
Unless anybody else makes more serious use of it than I do, I just use
it off and on.
> x11-wm/stumpwmjmglov
Maybe. I'm seeing if the upstream author is interested in havi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Following this month processing of the retirement batch, the following
packages have been reassigned to maintainer-needed and can take some
love. You know the drill, so if you want to maintain any of them please
add yourself to the metadata.xml.
packa
On Monday 03 November 2008 04:29:34 Nirbheek Chauhan wrote:
> Why not use EAPI=1 for those ebuilds and turn the flag on by default?
Well, as I said, it seems more sensible to me to set the default once, instead
of once for each ebuild. I don't particularly care, though, just making sure
people
On Monday 03 November 2008, Steve Long wrote:
> Peter Alfredsen wrote:
> > debug-print-function $FUNCNAME $*
>
> You should be using "$@" not unquoted $*.
Fixed. Also fixed base_src_unpack and base_src_compile calling their
grunt functions with $1, when clearly it should have been [EMAIL PROTECTE
В Вск, 02/11/2008 в 12:11 -0700, Gordon Malm пишет:
> You can cry "abuse" all you want. You FAIL to offer any alternatives or
> solutions. I'll ask again, how do you detect that you are compiling code
> destined to be run in-kernel from within gcc without checking for the
> __KERNEL__ macro?
Peter Alfredsen wrote:
> debug-print-function $FUNCNAME $*
You should be using "$@" not unquoted $*.
Seems like the FUNCNAME bit should just be rolled into the function
with "${FUNCNAME[1]}" which could be done tree-wide quite easily.
Ciaran McCreesh wrote:
> On Sun, 2 Nov 2008 12:11:10 -0700
> Gordon Malm <[EMAIL PROTECTED]> wrote:
>> > Have you conclusively established that they do build fine in
>> > parallel? If so, how?
>> Yes it builds in parallel. By compiling it in parallel.
> If you think compiling it in parallel con
