On Mon, 21 Jul 2014 23:01:44 + (UTC), James wrote:
> > Set PORT_LOGDIR in make.conf. This is not the same as the ELOG
> > settings, it logs the entire output from the ebuild.
>
> This sound workable. If I don't want something logged, just comment
> out the PORT_LGDIR in make.conf, or is th
Volker Armin Hemmann googlemail.com> writes:
> who told you that 'bloated' buzz word? The same people who told you
> about 'the cloud' or 'web 2.0'?
Nobody, common sense from practicle experience. Here's what you
*should* do to experince just how bloated most desktops have become.
Build up a
Neil Bothwick digimed.co.uk> writes:
> > What would folks suggest is the best way to capture the output
> > from the screen into a file (fancy formating?) as well as being
> > able see the local builds as they scroll the build out to
> > the terminal (screen) window (normal emerge results view
Am 21.07.2014 23:40, schrieb James:
> Stefan G. Weichinger xunil.at> writes:
>
>
Anyone playing with wayland already?
>>> Not yet.
>>> Closely related, is the QT5 approach to start experimenting.
>>> This might help [1]
>>> [1] http://qt-project.org/wiki/QtWayland
>> hmm, thanks ... I am
Stefan G. Weichinger xunil.at> writes:
> >> Anyone playing with wayland already?
>
> > Not yet.
> > Closely related, is the QT5 approach to start experimenting.
> > This might help [1]
> > [1] http://qt-project.org/wiki/QtWayland
> hmm, thanks ... I am not sure how to apply this
Most D
On Mon, 21 Jul 2014 16:54:36 + (UTC), James wrote:
> What would folks suggest is the best way to capture the output
> from the screen into a file (fancy formating?) as well as being
> able see the local builds as they scroll the build out to
> the terminal (screen) window (normal emerge result
Am 21.07.2014 15:54, schrieb James:
> Stefan G. Weichinger xunil.at> writes:
>
>
>> Anyone playing with wayland already?
>
> Not yet.
> Closely related, is the QT5 approach to start experimenting.
>
>> Maybe even using it as "daily driver" ?
>> I did some steps to compile and use it on my
On Mon, Jul 21, 2014 at 9:54 AM, James wrote:
> What would folks suggest is the best way to capture the output
> from the screen into a file (fancy formating?) as well as being
> able see the local builds as they scroll the build out to
> the terminal (screen) window (normal emerge results viewed
James wrote:
> Hello,
>
> I have some very large emerge builds going on
> with my /usr/local/portage experiments.
>
> What would folks suggest is the best way to capture the output
> from the screen into a file (fancy formating?) as well as being
> able see the local builds as they scroll the b
Hello,
I have some very large emerge builds going on
with my /usr/local/portage experiments.
What would folks suggest is the best way to capture the output
from the screen into a file (fancy formating?) as well as being
able see the local builds as they scroll the build out to
the terminal (scree
João Jerónimo gmail.com> writes:
>
> Hello.
>
> I installed the uclibc stage3 tarball no a x86 machine (I chose uclibc
> because the PC has only 256 MB of RAM).
Did you use one of these to install your system?
http://mirror.as24220.net/pub/gentoo/experimental/x86/uclibc/
Also note:
The i
Stefan G. Weichinger xunil.at> writes:
> Anyone playing with wayland already?
Not yet.
Closely related, is the QT5 approach to start experimenting.
> Maybe even using it as "daily driver" ?
> I did some steps to compile and use it on my systems ... so far I wasn't
> able to start up gnome
12 matches
Mail list logo
