On Sun, 7 Jun 2015 17:28:03 -0400
Mike Gilbert wrote:
> Sorry, I could I have sworn I saw something about "easier scripting"
> somewhere in the thread.
Now you have two problems. ;-)
jer
On Sun, 7 Jun 2015 04:40:47 + (UTC)
Duncan <1i5t5.dun...@cox.net> wrote:
> Well, yes, but vgacon is rather dated, now.
Never heard of a serial console? It's "dated" sure enough, but I for
one use them on a daily basis, and not by choice.
jer
On Sat, Jun 6, 2015 at 12:26 AM, Justin Lecher (jlec)
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Hi everyone,
>
> Can we get an agreement on how we are indenting metadata.xml?
>
> I like to properly format and indent metadata.xml, but without having
> an agreement or policy on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 06/08/2015 12:47 PM, William Hubbs wrote:
> On Sat, Jun 06, 2015 at 09:26:08AM +0200, Justin Lecher (jlec)
> wrote:
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA512
>>
>> Hi everyone,
>>
>> Can we get an agreement on how we are indenting metad
Duncan wrote:
> The point you made here was console-based workflow, as quoted above,
> and that's what I addressed, arguing that even if was valid at some
> point, it's no longer the factor it once was.
For you, that is. Be aware that this creates your bias. You can't
extrapolate from your own sit
Dnia 2015-06-08, o godz. 08:36:02
"Justin (jlec)" napisał(a):
> On 07/06/15 22:22, Michał Górny wrote:
> > Dnia 2015-06-07, o godz. 22:16:18
> > "Justin Lecher (jlec)" napisał(a):
> >
> >> -BEGIN PGP SIGNED MESSAGE-
> >> Hash: SHA512
> >>
> >> On 07/06/15 14:48, Andrew Udvare wrote:
> >
On Sat, Jun 06, 2015 at 09:26:08AM +0200, Justin Lecher (jlec) wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Hi everyone,
>
> Can we get an agreement on how we are indenting metadata.xml?
>
> I like to properly format and indent metadata.xml, but without having
> an agreement or
All,
here is the latest version of this eclass, which I will commit an hour
from now if no one has any objections.
Thanks,
William
# Copyright 2015 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Header: $
# @ECLASS: golang-vcs.eclass
# @MAINTAINER:
# Wi
then test the same hardware running Apache-mesos. So any
> suggestions you
> > have on that (so the comparisons are as similar as possible, including
> > recommended test codes) would be of keen interest to me.
> >
> >
> > James
> >
s, Apache-spark, Apache-storm and tachyon. It'd be great to
> > run some tests of codes on openstack (running on local hardware) and
> > then test the same hardware running Apache-mesos. So any suggestions you
> > have on that (so the comparisons are as similar as possib
sts of codes on openstack (running on local hardware) and
> then test the same hardware running Apache-mesos. So any suggestions you
> have on that (so the comparisons are as similar as possible, including
> recommended test codes) would be of keen interest to me.
>
>
> James
>
&
On 06/08/2015 10:30 AM, Matthew Thode wrote:
Hi,
I've just started generation of Gentoo Openstack images. Right now it
is just a basic amd64 image, but I plan on adding nomultilib and
hardened variants (for a total of at least 4 images). I plan on
generating these images at least weekly.
Thes
Andrew Savchenko posted on Mon, 08 Jun 2015 16:33:55 +0300 as excerpted:
> On Sun, 7 Jun 2015 04:40:47 + (UTC) Duncan wrote:
>> Andrew Savchenko posted on Sat, 06 Jun 2015 20:36:13 +0300 as
>> excerpted:
>>
>> > It will never be finished, because console-based workflow is the most
>> > effici
Hi,
I've just started generation of Gentoo Openstack images. Right now it
is just a basic amd64 image, but I plan on adding nomultilib and
hardened variants (for a total of at least 4 images). I plan on
generating these images at least weekly.
These images are not yet sanctioned by our infra te
Franz Fellner wrote:
>
> IMHO a working build system
> always is better than a fast but potentially broken one :)
Meanwhile, it is not so clear which of the two systems
is more likely the "potentially broken" one:
According to some of the mentioned bugs, it appears to me
that some upstreams consi
On Sun, 7 Jun 2015 04:40:47 + (UTC) Duncan wrote:
> Andrew Savchenko posted on Sat, 06 Jun 2015 20:36:13 +0300 as excerpted:
>
> > On Sat, 06 Jun 2015 18:35:41 +0600 Vadim A. Misbakh-Soloviov wrote:
> >> > * linewidth >> 80 (why do we have this short limit still in 2015)
> >>
> >> Actually, I
On 06/08/2015 02:01 PM, Michał Górny wrote:
> Dnia 2015-06-08, o godz. 12:46:42
> hasufell napisał(a):
>
>> On 06/07/2015 05:08 PM, Michał Górny wrote:
>>> Hello, developers.
>>>
>> [...]
>>
>> It's not clear to me how the transition should look like.
>>
>> Are you suggesting Ninja to be the new
Michał Górny wrote:
> Dnia 2015-06-08, o godz. 12:46:42
> hasufell napisał(a):
>
> > On 06/07/2015 05:08 PM, Michał Górny wrote:
> > > Hello, developers.
> > >
> > [...]
> >
> > It's not clear to me how the transition should look like.
> >
> > Are you suggesting Ninja to be the new default or
Dnia 2015-06-08, o godz. 12:46:42
hasufell napisał(a):
> On 06/07/2015 05:08 PM, Michał Górny wrote:
> > Hello, developers.
> >
> [...]
>
> It's not clear to me how the transition should look like.
>
> Are you suggesting Ninja to be the new default or do you want to switch
> per-packages after
On 06/07/2015 05:08 PM, Michał Górny wrote:
> Hello, developers.
>
[...]
It's not clear to me how the transition should look like.
Are you suggesting Ninja to be the new default or do you want to switch
per-packages after having tested them?
If the former, then we need a tinderbox-run.
Christoph Junghans posted on Sun, 07 Jun 2015 20:08:25 -0600 as excerpted:
> 2015-06-07 14:19 GMT-06:00 Justin Lecher (jlec) :
>>
>> On 07/06/15 22:14, Johannes Huber wrote:
>>
>>> Am Sonntag 07 Juni 2015, 17:08:57 schrieb Michał Górny:
>>>
CMake sucks a lot [but will suck less if we switch]
21 matches
Mail list logo
