On 14:18 Wed 06 Aug , Robin H. Johnson wrote:
> Getting the bot out there
> -
> If you would like to have the new bot in your #gentoo-* channel, would
> each channel founder/leader please respond to this thread, stating the
> channel name, and that they are the contact f
* "Robin H. Johnson" <[EMAIL PROTECTED]>:
> Getting the bot out there
> -
> If you would like to have the new bot in your #gentoo-* channel, would
> each channel founder/leader please respond to this thread, stating the
> channel name, and that they are the contact for any p
Zac Medico wrote:
> As a substitute for the previously discussed RESTRICT=live value[1],
> I'd now like you to consider an equivalent PROPERTIES=live-sources
> setting. By specifying PROPERTIES=live-sources, an ebuild will be
> able to indicate that it uses src_unpack() to download sources from
>
On Wed, 2008-08-06 at 14:18 -0700, Robin H. Johnson wrote:
> Getting the bot out there
> -
> If you would like to have the new bot in your #gentoo-* channel, would
> each channel founder/leader please respond to this thread, stating the
> channel name, and that they are the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeremy Olexa wrote:
>> Please consider a new PROPERTIES=interactive setting that allows an
>> ebuild to indicate that it uses stdin and stdout for user
>
> I don't think anyone will disagree with this one. The one problem that I
> see is that if the e
On 14:18 Wed 06 Aug , Robin H. Johnson wrote:
> Hi folks,
>
> Sorry that it's taken this long to get completed, but the Jeeves
> replacement, Willikins, is finally 99% done, and ready to join lots of
> channels.
w
>
> Getting the bot out there
> -
On Wed, Aug 6, 2008 at 9:27 PM, Jeremy Olexa <[EMAIL PROTECTED]> wrote:
>> Please consider a new PROPERTIES=interactive setting that allows an
>> ebuild to indicate that it uses stdin and stdout for user
>
> I don't think anyone will disagree with this one. The one problem that I see
> is that if t
Please consider a new PROPERTIES=interactive setting that allows an
ebuild to indicate that it uses stdin and stdout for user
I don't think anyone will disagree with this one. The one problem that I
see is that if the ebuild still doesn't have this value in it, portage
will *look* like it has
Robin H. Johnson yazmış:
> Hi folks,
>
> Sorry that it's taken this long to get completed, but the Jeeves
> replacement, Willikins, is finally 99% done, and ready to join lots of
> channels.
>
Thanks!
> Getting the bot out there
> -
> If you would like to have the new bo
On Thu, Aug 07, 2008 at 12:12:16PM +1000, Nathan Sullivan wrote:
> Arch channels? #gentoo-amd64 and #gentoo-amd64-dev would be cool :) i tend
> to use jeeves a bit in amd64-dev...
Please have the channel founder or point of contact request it.
--
Robin Hugh Johnson
Gentoo Linux Developer & Infra
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Robin H. Johnson wrote:
| Hi folks,
|
| Sorry that it's taken this long to get completed, but the Jeeves
| replacement, Willikins, is finally 99% done, and ready to join lots of
| channels.
|
| Getting the bot out there
| -
| I
Arch channels? #gentoo-amd64 and #gentoo-amd64-dev would be cool :) i tend
to use jeeves a bit in amd64-dev...
Nathan Sullivan.
On Thu, Aug 7, 2008 at 10:20 AM, Mike Pagano <[EMAIL PROTECTED]> wrote:
> On Wednesday 06 August 2008 17:18:05 Robin H. Johnson wrote:
> > Hi folks,
> >
> > Sorry that
On Wednesday 06 August 2008 17:18:05 Robin H. Johnson wrote:
> Hi folks,
>
> Sorry that it's taken this long to get completed, but the Jeeves
> replacement, Willikins, is finally 99% done, and ready to join lots of
> channels.
>
#gentoo-kernel
Thanks to everyone involved.
--
Mike Pagano
Gentoo
Robin H. Johnson wrote:
If you would like to have the new bot in your #gentoo-* channel, would
each channel founder/leader please respond to this thread, stating the
channel name, and that they are the contact for any problems/troubles.
#gentoo-python
Thanks
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Robin H. Johnson wrote:
> Getting the bot out there
> -
> If you would like to have the new bot in your #gentoo-* channel, would
> each channel founder/leader please respond to this thread, stating the
> channel name, and that t
On 2008-08-06 23:18, Robin H. Johnson wrote:
Hi folks,
Sorry that it's taken this long to get completed, but the Jeeves
replacement, Willikins, is finally 99% done, and ready to join lots of
channels.
Getting the bot out there
-
If you would like to have the new bot in y
Robin H. Johnson kirjoitti:
Hi folks,
Sorry that it's taken this long to get completed, but the Jeeves
replacement, Willikins, is finally 99% done, and ready to join lots of
channels.
Getting the bot out there
-
If you would like to have the new bot in your #gentoo-* cha
On 06-08-2008 14:18:05 -0700, Robin H. Johnson wrote:
> Getting the bot out there
> -
> If you would like to have the new bot in your #gentoo-* channel, would
> each channel founder/leader please respond to this thread, stating the
> channel name, and that they are the conta
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2008.08.06 22:18, Robin H. Johnson wrote:
> Hi folks,
>
> Sorry that it's taken this long to get completed, but the Jeeves
> replacement, Willikins, is finally 99% done, and ready to join lots
> of
> channels.
Robin
Can Willikins be joined to:-
"Robin H. Johnson" <[EMAIL PROTECTED]> said:
> Getting the bot out there
> -
> If you would like to have the new bot in your #gentoo-* channel, would
> each channel founder/leader please respond to this thread, stating the
> channel name, and that they are the contact for an
On 14:18 Wed 06 Aug , Robin H. Johnson wrote:
> Sorry that it's taken this long to get completed, but the Jeeves
> replacement, Willikins, is finally 99% done, and ready to join lots of
> channels.
Yay!
> Getting the bot out there
> -
> If you would like to have the ne
Hi folks,
Sorry that it's taken this long to get completed, but the Jeeves
replacement, Willikins, is finally 99% done, and ready to join lots of
channels.
Getting the bot out there
-
If you would like to have the new bot in your #gentoo-* channel, would
each channel found
That's a bit sad that I announce this as I learnt caml with it, too many
years ago.
Reasons:
Does not build (bug #206138), unmaintained upstream for years, not
very useful nowadays. Use dev-lang/ocaml instead.
Alexis.
signature.asc
Description: PGP signature
On Wed, Aug 6, 2008 at 8:19 PM, Chrissy Fullam <[EMAIL PROTECTED]> wrote:
> It could be a good precedent without being policy, or dependent upon the
> reason for being forcibly removed perhaps. It is quite possible for someone
> to find another way to contribute without having developer status, a
> 2) Continued presence of forcefully retired devs It really baffles me that
> some developers are forcefully retired for anti-social behavior, but are
> not consequently banned from the places where they display this behavior,
> such as our MLs and IRC channels. What good is it to retire developer
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ciaran McCreesh wrote:
> What's wrong with just discussing it until we agree? Why do you think a
> compromise is necessary?
I think voting might be an interesting approach. We'll see if anyone
else is interested. I don't know yet. :)
Zac
-BEGIN
On Wed, 06 Aug 2008 04:03:02 -0700
Zac Medico <[EMAIL PROTECTED]> wrote:
> Given the vast number of possible choices to consider when defining
> new PROPERTIES values [1], perhaps we should create a ballot and
> hold a vote on definitions that people have submitted. I suppose
> that voters would be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello everyone,
Given the vast number of possible choices to consider when defining
new PROPERTIES values [1], perhaps we should create a ballot and
hold a vote on definitions that people have submitted. I suppose
that voters would be able to vote yes
On Fri, 01 Aug 2008 19:02:48 -0700
Zac Medico <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi everyone,
>
> It might good to add support for a new RESTRICT=live value in
> ebuilds. By specifying this value, an ebuild would be able to
> indicate that it uses sr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alec Warner wrote:
>> Just to be clear; PROPERTIES is a space separated list of items correct?
I was thinking that it might support the same syntax as RESTRICT,
which includes support for USE conditionals.
Zac
-BEGIN PGP SIGNATURE-
Version: G
On Wed, Aug 6, 2008 at 2:22 AM, Zac Medico <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hello again,
>
> Please consider a new PROPERTIES=interactive setting that allows an
> ebuild to indicate that it uses stdin and stdout for user
> interaction sometime during
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello again,
Please consider a new PROPERTIES=interactive setting that allows an
ebuild to indicate that it uses stdin and stdout for user
interaction sometime during the pkg_setup and/or src_unpack phases
(similar to GLEP 52 [1]). This will be anothe
On 06.08.2008 11:11, Thilo Bangert wrote:
> "Robin H. Johnson" <[EMAIL PROTECTED]> said:
>> Please do NOT use out-of-office, vacation or any other auto-responders
>> on the lists. It's bad list etiquette.
>
> decent vacation mail software ignores mail marked with a 'Precedence:
> bulk' header, as
"Robin H. Johnson" <[EMAIL PROTECTED]> said:
> Please do NOT use out-of-office, vacation or any other auto-responders
> on the lists. It's bad list etiquette.
decent vacation mail software ignores mail marked with a 'Precedence:
bulk' header, as mailing list mail usually is (including mails sent
34 matches
Mail list logo
